From owner-freebsd-hackers Fri Jul 21 17: 2:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 71EC737C29E for ; Fri, 21 Jul 2000 17:02:45 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e6M02iD05553 for ; Fri, 21 Jul 2000 17:02:45 -0700 (PDT) Date: Fri, 21 Jul 2000 17:02:44 -0700 (PDT) From: Doug White To: hackers@freebsd.org Subject: suprising mount root behavior Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, Some new root mount behavior in 4.0 just saved my bacon, but I'm curious as to how it's implemented. My custom installer accidentally created fstab entries for IDE disks on a SCSI-only system. Thus, fstab point to /dev/ad0s1a for / and /dev/ad0s1b for swap. I rebooted the system to try and fix it, and lo and behold it booted up correctly! I had no swap but root was mounted RW so I could fix the fstab. Now my question is: How did it know? I'm not setting vfs.root.mountfrom in the loader. Also, how did mount know to not override the / mountpoint to the one from fstab (and subsequently fail)? Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message