From owner-freebsd-current Wed Oct 23 14:15:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA11881 for current-outgoing; Wed, 23 Oct 1996 14:15:48 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA11875 for ; Wed, 23 Oct 1996 14:15:45 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA10460; Wed, 23 Oct 1996 14:13:20 -0700 From: Terry Lambert Message-Id: <199610232113.OAA10460@phaeton.artisoft.com> Subject: Re: HEY! mount -u -o ro / now works! To: julian@whistle.com (Julian Elischer) Date: Wed, 23 Oct 1996 14:13:20 -0700 (MST) Cc: current@freebsd.org In-Reply-To: <326D4BCF.41C67EA6@whistle.com> from "Julian Elischer" at Oct 22, 96 03:33:51 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > who enabled that? > why was it not announced? > is there a 'gotcha'? > > does it sync everything before changing it to ro? > > neat! but , can I trust it? Check the commit messages. Jeffrey Hsu might have done it. If not, beware: it did not formerly work. I got it working as part of my mount code changes for integrating root and non-root mount handling, and pushing root vs. inferior mounting up to the common code layer (where it belings). I had to do it for the Win95 version of the VFS framework, since Win95 insists that FS's be mounted each on its own virtual root (one FS, one drive letter). The read-only mount fix was a side-effect of allowing a mount before fsck to get the drive ID allocated to the device. This was part of the code I back-ported and submitted a year ago last June. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.