From owner-freebsd-questions Tue Mar 24 17:38:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05833 for freebsd-questions-outgoing; Tue, 24 Mar 1998 17:38:43 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from tera.com (tera.tera.com [207.108.223.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05815 for ; Tue, 24 Mar 1998 17:38:35 -0800 (PST) (envelope-from kline@tao.thought.org) Received: (from uucp@localhost) by tera.com (8.7.5/8.7.3) with UUCP id RAA17623 for freebsd-questions@FreeBSD.ORG; Tue, 24 Mar 1998 17:37:59 -0800 (PST) Received: (from kline@localhost) by tao.thought.org (8.8.5/8.7.3) id RAA17066; Tue, 24 Mar 1998 17:37:35 -0800 (PST) From: Gary Kline Message-Id: <199803250137.RAA17066@tao.thought.org> Subject: Re: Cannot mount "/" after cvsup to 2.2.6-BETA ! In-Reply-To: From kline at "Mar 24, 98 12:41:31 pm" To: kline@tao.thought.org (kline) Date: Tue, 24 Mar 1998 17:37:35 -0800 (PST) Cc: freebsd-questions@FreeBSD.ORG (fquestions) Organization: <> thought.org: public access uNix in service... <> X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Jose M. Alcaide: > Patrik Åström wrote: > > > > This morning I did a CVSUP to recompiled my kernel and after installed > > it and rebooted I got the error message. > > > > /dev/sd0a on /: Specified device does not match mounted device, > > filesystem mount failed. > > > > >From Mike Smith : > > 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. > I've seen discussions on this name-change on the -stable list recently. Your posting clears things up somewhat, thanks. Two questions here. Given my current fs table entriy on my P90:: pd 12:04 [230] cat /etc/fstab /dev/sd0a / ufs rw 1 1 /dev/sd0s1b none swap sw 0 0 /dev/sd0s1e /usr ufs rw 1 1 /dev/sd0s1f /var ufs rw 1 1 /dev/sd0s1g /home ufs rw 1 1 # ## SCSI drive #2 # /dev/sd1c /usr/local ufs rw 1 1 proc /proc procfs rw 0 0 /dev/cd0a /cdrom cd9660 ro, noauto 0 0 Would my _only_ fstab change for 2.2.6 involve this:: /dev/sd0s1a / ufs rw 1 1 ? /* ...If the root-name change is this straightforward, a script should be able to do it. */ My second question is Why this hack? If this is for greater flexibility of some kind, fine. But for aesthetics? dunno... gary -- Gary D. Kline kline@tao.thought.org Public service uNix -- Gary D. Kline kline@tao.thought.org Public service uNix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message