On Wed, 27 Nov 2002, Robert Watson wrote: > 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? > > 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.
Why can't they be changed? All the other tunefs flags except FS_ACLS and FS_MULTILABEL are related to writing, so ffs_reload() has to support them changing as a side effect of supporting transitions from read-only to read-write mode. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message