Date: Wed, 11 Feb 1998 09:44:41 -0800 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: Mike Smith <mike@smith.net.au> Cc: "Jordan K. Hubbard" <jkh@FreeBSD.ORG>, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-release@FreeBSD.ORG Subject: Re: cvs commit: src/release/sysinstall devices.c floppy.c install.c menus.c Message-ID: <24136.887219081@time.cdrom.com> In-Reply-To: Your message of "Wed, 11 Feb 1998 09:40:47 PST." <199802111740.JAA00580@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > MFC: create devices only as needed. Gosh I sure wish those "extra" 56 > > bytes in the boot blocks could be used to TEACH THE BOOT BLOCKS ABOUT > > SLICES SO WE COULD GET RID OF THE %$#@*!! ROOT COMPATABILITY HACK. > > While I'm wishing, I'd like world peace too. > > You want the bootblocks to know which slice they're loaded from, right? > > I can do this, but it will mean that anyone wanting to boot a 2.2.6+ > kernel *must* update their bootblocks. Why? If they have the old boot blocks then all that should be required is that they have root on "/dev/wd0a" instead of "/dev/wd0s2a", or whatever, which is something that'll be the case anyway if they upgraded since their /etc/fstab file will have been preserved. I'm just looking to make the "/dev/wd0s2a" case work without the kernel yelling that the root device booted from was not the one we have listed in /etc/fstab, leading to boot failure. Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?24136.887219081>