Date: Tue, 20 Jun 1995 04:17:06 +1000 From: Bruce Evans <bde@zeta.org.au> To: bde@zeta.org.au, rgrimes@gndrsh.aac.dev.com Cc: bugs@FreeBSD.org Subject: Re: 2.05R panics on boot Message-ID: <199506191817.EAA12339@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
>> >I think you really meant to say ``hd(1,a) becomes sd0a, which...'' >> >> I meant what I said. It can't have become sd0a because then wd0 >> wouldn't have been looked at. It only becomes sd0a if the disklabel >> type is DTYPE_SCSI. sd(0,a) becomes wd0a for the same reason. >> sysinstall sets the disklabel type correctly under the assumption that >> scsi disk names start with 's'. Typing hd(*, *) has no effect on the >> FreeBSD major device. It only forces the FreeBSD unit number to 0. >Then something has been changed in what is going on in >the boot code with respect to hd(X,a), as this *DID* cause bootdev >to be set to sd(X-1,a). And these comments are now need of updating: >README.386BSD:use device 'hd' >README.386BSD:hd is special in that the kernel is always told to use unit 0, >README.serial: Use hd(1,a)/kernel to boot sd0 when wd0 is also installed. >boot.c: "Use hd(1,a)/kernel to boot sd0 when wd0 is also installed.\n" Nothing has changed. The documentation just doesn't tell you what happens in unsupported cases. The only supported case is booting from sd0 when wd0 (and perhaps other wd's) are installed. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506191817.EAA12339>