Date: Wed, 10 Feb 2010 23:05:12 -0800 From: Julian Elischer <julian@elischer.org> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-hackers@freebsd.org, Peter Steele <psteele@maxiscale.com> Subject: Re: How can I force boot from alternate drive with boot.config? Message-ID: <4B73AC28.2000402@elischer.org> In-Reply-To: <201002100838.11381.jhb@freebsd.org> References: <7B9397B189EB6E46A5EE7B4C8A4BB7CB383B2699@MBX03.exg5.exghost.com> <23F2E2B0457F4046AD8350DAFB86C41130D434E7@MBX03.exg5.exghost.com> <7B9397B189EB6E46A5EE7B4C8A4BB7CB3849F770@MBX03.exg5.exghost.com> <201002100838.11381.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin wrote: > I think the unit number is largely ignored now. The kernel used to believe it > for finding /, but the loader now reads /etc/fstab and sets a variable in kenv > to tell the kernel where to find /. One of the most annoying "improvements" for the decade from my perspective.. because if / is not going to be where the loader thinks / is (because that is a different F with a different /etc/fstab) then you need to do lots of fancy footwork to undo the damage. Oh and it's not terribly well documented how to get around it. (that I've found)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B73AC28.2000402>