Date: Fri, 04 Jan 2002 14:13:40 -0800 (PST) From: John Baldwin <jhb@FreeBSD.org> To: Bruce Evans <bde@zeta.org.au> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: RE: cvs commit: src/sys/boot/i386/libi386 bootinfo.c Message-ID: <XFMail.020104141340.jhb@FreeBSD.org> In-Reply-To: <20020105072719.C21854-100000@gamplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04-Jan-02 Bruce Evans wrote: > 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. Well, that's a bit tricky. In the loader, all I know is that the BIOS cd cd0 is _some_ CD device. I don't know which device. It could be cd4 or acd0 to the kernel. I'm not sure how best to go about that. :( > Bruce -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ 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?XFMail.020104141340.jhb>