From owner-freebsd-current Sun Sep 27 01:16:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29111 for freebsd-current-outgoing; Sun, 27 Sep 1998 01:16:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA29098 for ; Sun, 27 Sep 1998 01:16:14 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id SAA01864; Sun, 27 Sep 1998 18:16:02 +1000 Date: Sun, 27 Sep 1998 18:16:02 +1000 From: Bruce Evans Message-Id: <199809270816.SAA01864@godzilla.zeta.org.au> To: jb@cimlogic.com.au, peter@netplex.com.au Subject: Re: Upgrade documentation (Was: Re: Make world error on -current elf) Cc: current@FreeBSD.ORG, Studded@dal.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Incidently, I had to back out the /dev/sd0a <-> /dev/sd0s1a mount device >changes for / in /etc/fstab. I'm not sure how this works.. Will a 3.x >system deal with an old-style 'sd0a' or 'wd0a' line in /etc/fstab? That change is a real pain for testing old kernels. I used /dev/sd0a on most of my systems for backwards compatibility. This works except when fsck needs to run. 3.x will certainly accept sd0a for dedicated disks, since there is no sd0s1 then. What should happen is for mount(8) and fsck(8) to get the name of the root device from the kernel using fsstat(), and use it instead of the fstab entry unless it is the useless dummy name "root_device" returned by old kernels. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message