From owner-cvs-release Wed Feb 11 09:45:12 1998 Return-Path: Received: (from daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09319 for cvs-release-outgoing; Wed, 11 Feb 1998 09:45:12 -0800 (PST) (envelope-from owner-cvs-release) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09305; Wed, 11 Feb 1998 09:44:59 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id JAA24142; Wed, 11 Feb 1998 09:44:44 -0800 (PST) To: Mike Smith cc: "Jordan K. Hubbard" , 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 In-reply-to: Your message of "Wed, 11 Feb 1998 09:40:47 PST." <199802111740.JAA00580@dingo.cdrom.com> Date: Wed, 11 Feb 1998 09:44:41 -0800 Message-ID: <24136.887219081@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-cvs-release@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > 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