Date: Wed, 31 May 2006 23:25:43 -0600 From: Scott Long <scottl@samsco.org> To: Craig Rodrigues <rodrigc@crodrigues.org> Cc: Joe Marcus Clarke <marcus@freebsd.org>, current@freebsd.org Subject: Re: -CURRENT does not recognize standard mount options Message-ID: <447E7A57.6050700@samsco.org> In-Reply-To: <20060531154439.GA5528@crodrigues.org> References: <1148962081.8820.49.camel@shumai.marcuscom.com> <20060530160405.GA39658@crodrigues.org> <1149006607.94908.5.camel@shumai.marcuscom.com> <20060531154439.GA5528@crodrigues.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Craig Rodrigues wrote: > On Tue, May 30, 2006 at 12:30:07PM -0400, Joe Marcus Clarke wrote: > >>Should its kernel backend not support all of those options as well? Or >>perhaps global_opts in vfs_mount.c should be updated to support all > > > Can you try this patch? I'm not sure if "force" and "sync" > should be global_opts or not because I don't know They are no more global than the ACL or multilabel options, not to mentiont he NFS-specific options. > if they make sense for every FS, but for symmetry with what was > in mount_msdosfs before, we can push them into the filesystem code for msdosfs. > These inconsistencies between the various mount programs and > the various filesystem code is why I've been trying to push > towards using a single mount binary, and pushing the mount option > parsing into vfs_mount.c and the code for the specific filesystem. > We are not quite there yet, but we are a lot closer. > Thanks for doing the un-fun job of unwinding all of this. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?447E7A57.6050700>