From owner-freebsd-stable Mon Mar 23 17:14:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01820 for freebsd-stable-outgoing; Mon, 23 Mar 1998 17:14:30 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA01805 for ; Mon, 23 Mar 1998 17:14:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id RAA14594 for ; Mon, 23 Mar 1998 17:11:07 -0800 (PST) Message-Id: <199803240111.RAA14594@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: FreeBSD-Stable@FreeBSD.ORG Subject: Re: Important questions regarding the new slice code In-reply-to: Your message of "Mon, 23 Mar 1998 15:52:51 PST." <27566.890697171@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Mar 1998 17:11:05 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > The only thing you should be clued about here is updating /etc/fstab > > (maybe this is re-written for you, too - I don't remember). > > It is not, and the clue about updating was just added to the final > confirmation dialog. :) Just to clarify here; the original plan was to have it automagically updated, but there are some unpleasant corner cases here where the result would be a plastered configuration, and I don't think anyone wants that. So instead, here's some text to explain the situation. It needs to be somewhere prominent (for upgraders anyway). ---- FreeBSD 2.2.6 introduces a change in the naming of the device from which the root filesystem is mounted. This change affects all systems, however user intervention is only required for systems undergoing an upgrade installation. Previously, the root filesystem was always mounted from the compatability slice, while other partitions on the same disk were mounted from their true slice. This might, for example, have resulted in an /etc/fstab file like: # Device Mountpoint FStype Options Dump Pass# /dev/wd0s2b none swap sw 0 0 /dev/wd0a / ufs rw 1 1 /dev/wd0s2f /local0 ufs rw 1 1 /dev/wd0s2e /usr ufs rw 1 1 For FreeBSD 2.2.6 and later, this format changes so that the device for '/' is consistent with others, ie. # Device Mountpoint FStype Options Dump Pass# /dev/wd0s2b none swap sw 0 0 /dev/wd0s2a / ufs rw 1 1 /dev/wd0s2f /local0 ufs rw 1 1 /dev/wd0s2e /usr ufs rw 1 1 On a new installation, this change is handled automatically by Sysinstall. For an upgrade where the local configuration information is preserved, the user must make this change manually, by editing /etc/fstab. THIS CHANGE IS EXTREMELY IMPORTANT. If /etc/fstab is not updated manually in this case, the system will issue a warning message whenever / is mounted (normally at startup) indicating the change that must be made. In addition, trouble may be experienced if the root filesystem is not correctly unmounted, whereby the root filesystem will not be marked clean at the next reboot. ---- Note that whilst the procedure for the not-clean problem is reasonably straightforward, this is probably not the place to document it. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message