Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel!munnari.oz.au!uunet!super!rminnich From: rminnich@super.org (Ronald G Minnich) Subject: Re: 386BSD & COMPAQ 486/33 Message-ID: <1992Sep8.135113.737@super.org> Sender: news@super.org (USENET News System) Nntp-Posting-Host: metropolis Organization: Supercomputing Research Center (Bowie, MD) References: <1992Sep7.112452.5403@csd.uch.gr> <1992Sep8.023138.25145@super.org> <92252.095938HEUER@DMSWWU1A.UNI-MUENSTER.DE> Date: Tue, 8 Sep 1992 13:51:13 GMT Lines: 26 In article <92252.095938HEUER@DMSWWU1A.UNI-MUENSTER.DE> Stephan Heuer <HEUER@DMSWWU1A.UNI-MUENSTER.DE> writes: >I have 386BSD 0.1 running on a Compaq Deskpro 386/20 with 387, >ethernet and 60MB hard disk. 0.1 refused to boot, but I had 0.0 running >so I used the 0.0 boot block. I just copied the first 8k from the 0.0 >boot disk to the 0.1 boot disk and voila ... I have *not* changed my 0.0 >disklabel on the hard disk! I have been told that jolitz has a Compaq Deskpro 386/20, so am not surprised you can get going. If i use the 0.0 bootstrap on the 0.1 dist.fs, the 0.1 kernel comes up and init dies. So using the 0.0 boot track for 0.1 may or may not work; your mileage will definitely vary. note that 0.0 boot track is kind of broken anyway: it can't boot reasonably large kernels, i.e. kernels with NFS. And the boot block sources on 0.0 don't build a working secondary bootstrap (primary block 0 bootstrap does build fine, however, once you fix /bin/ld on 0.0-- you have to take out a hack that makes -n not build the proper type of file). ron -- -------------------------------------------------------------------------------- satisfaction: the feeling you get when you | rminnich@super.org run newfs on a DOS disk so you can install 386BSD.| (301)-805-7451 Now if only I could do this to AIX on the RS/6k ...|