From owner-freebsd-current Wed Nov 27 10:19: 6 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 19EDC37B401 for ; Wed, 27 Nov 2002 10:19:05 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84E7943EBE for ; Wed, 27 Nov 2002 10:19:04 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.6/8.12.5) with SMTP id gARIIvBF052466; Wed, 27 Nov 2002 13:18:59 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Wed, 27 Nov 2002 13:18:57 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Bruce Evans Cc: bsdc@xtremedev.com, Hiten Pandya , current@FreeBSD.ORG Subject: Re: ACLs on the boot partition? In-Reply-To: <20021127195019.W7258-100000@gamplex.bde.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 27 Nov 2002, Bruce Evans wrote: > On Tue, 26 Nov 2002, Robert Watson wrote: > > > tunefs changes the flag for the next mount, so doesn't take immediate > > effect. Once you've tunefs'd a read-only file system, you need to unmount > > and remount it -- for the file system root, this generally means > > rebooting. Just to confirm: you're running with GENERIC, or with a kernel > > Er, what is the mount(..., MNT_RELOAD ...) in tunefs for then? > Unmounting and remounting should not be necessary for any read-only file > system including "/". You can do the MNT_RELOAD from the command line > using mount -u if tunefs doesn't do it. > > I have some old fixes for tunefs which fix missing remounts as a side > effect. In -current, tunefs only detects mounted filesystems if they > are in fstab. It clobbers read-write mounted filesystems and fails to > remount read-only mounted file systems if they are not detected. The problem is that some flags can't be changed via MNT_RELOAD and require a from-scratch mount. I'm hoping that with nmount(), we can get a little more expressive regarding what changes are (and aren't) allowed to flags. Right now there's some uncomfortable masking. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message