Date: Sat, 5 Jan 2002 07:29:23 +1100 (EST) From: Bruce Evans <bde@zeta.org.au> To: John Baldwin <jhb@FreeBSD.org> Cc: <cvs-all@FreeBSD.org>, <cvs-committers@FreeBSD.org> Subject: RE: cvs commit: src/sys/boot/i386/libi386 bootinfo.c Message-ID: <20020105072719.C21854-100000@gamplex.bde.org> In-Reply-To: <XFMail.020104014417.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 4 Jan 2002, John Baldwin wrote: > On 04-Jan-02 John Baldwin wrote: > > jhb 2002/01/03 23:59:27 PST > > > > Modified files: > > sys/boot/i386/libi386 bootinfo.c > > Log: > > Don't turn on RB_CDROM if the rootdev is a BIOS cd device for now as this > > breaks when cdboot is used with an MFS root. > > This isn't really right. The problem is that for an MFS root, we leave the > root dev in the loader pointing to whatever, and RB_CDROM takes precedence over > MD_ROOT. A more proper fix might be to allow the rootdev to be set to "mfs" or > "md0" or some such and have the loader allow that. Then if the user leaves cd0 I thought that RB_CDROM was only set by the old bootblocks. Bootblocks that are less than 2 years old should set vfs.root.mountfrom to <vfsname>[:<path>], and not shoot their foot off by setting deprecated flags. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020105072719.C21854-100000>