Date: Tue, 10 Mar 1998 20:59:43 -0800 From: Mike Smith <mike@smith.net.au> To: Bruce Evans <bde@zeta.org.au> Cc: current@FreeBSD.ORG, jmz@cabri.obs-besancon.fr Subject: Re: Panic with the new slice stuff Message-ID: <199803110459.UAA21625@dingo.cdrom.com> In-Reply-To: Your message of "Wed, 11 Mar 1998 15:24:23 %2B1100." <199803110424.PAA25533@godzilla.zeta.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> > It should be fixed in the current vfs_conf.c, except for the bogus device > name in the "changing" message. This is not easy to fix, since it is > not known until later that slice == 5 (sd0s4, not sd0s5) passed by the > boot blocks really means slice == 0, (sd0, not sd0s-1). Yeah. Any suggestions on this would be gratefully appreciated. I'm leaning towards masking the slice number in the device comparison when it decides whether to emit the message. Test results today showed up a number of interesting things: - disklabel -rwB ... auto on a virgin disk will not set the disk type correctly. This confuses the bootstrap if the disk in question is a SCSI disk, as it defaults to IDE, causing the root mount to fail. - if you supply 'sd' instead of 'wd' at the prompt, the bootstrap will ignore you and go with what it gets from the disklabel. (bootstrap from -stable in both cases) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199803110459.UAA21625>