From: "Steve French" <smfrench@gmail.com>
To: "Miklos Szeredi" <miklos@szeredi.hu>
Cc: raven@themaw.net, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
kzak@redhat.com, ericvh@gmail.com, lucho@ionkov.net,
zippel@linux-m68k.org, hpa@zytor.com, rathamahata@php4.ru,
dhowells@redhat.com, sfrench@samba.org, mhalcrow@us.ibm.com,
phillip@hellewell.homeip.net, hirofumi@mail.parknet.co.jp,
mikulas@artax.karlin.mff.cuni.cz, wli@holomorphy.com,
shaggy@austin.ibm.com, vandrove@vc.cvut.cz,
trond.myklebust@fys.uio.no, aia21@cantab.net,
mark.fasheh@oracle.com, kurt.hackel@oracle.com,
reiserfs-devel@vger.kernel.org, bfennema@falcon.csc.calpoly.edu,
dushistov@mail.ru, xfs-masters@oss.sgi.com, arnd@arndb.de,
holzheu@de.ibm.com
Subject: Re: request for patches: showing mount options
Date: Fri, 27 Jul 2007 11:04:12 -0500 [thread overview]
Message-ID: <524f69650707270904j24038282le55f3981dff560a@mail.gmail.com> (raw)
In-Reply-To: <E1IERvH-00016M-00@dorka.pomaz.szeredi.hu>
cifs and nfs (probably others) have some mount options which are mount
order dependent ie may be invalid or ignored when you have more than
one mount to the same server, or mount the same resource in two places
with different options. In the long run, at least for cifs, we may be
able to better handle a user mounting to the same server twice with
e.g. different security options (authentication, packet signing ...),
but in the meantime are there any thoughts on whether those type of
mount options should be displayed differently
On 7/27/07, Miklos Szeredi <miklos@szeredi.hu> wrote:
> > all - fs has options, but doesn't define ->show_options()
> > some - fs defines ->show_options(), but some options are not shown
> > noopt - fs does not have options
> > good - fs shows all options
> > patch - I have a patch
>
> [...]
>
> > > autofs all
> >
> > I'm not sure I understand this.
> > How does autofs show it's options without a ->show_options method?
>
> It doesn't. The "all" means, all of them need to be added to
> ->show_options(), not that all are shown.
>
> I can see now that this is slightly confusing, sorry.
>
> So the ones that need attention are "all" and "some". The others are
> fine in theory. Of course I may have missed something.
>
> > > autofs4 some
> >
> > OK, uid and gid aren't shown.
> > That should be straight forward to fix.
> > What's your time frame for this?
>
> ASAP ;)
>
> 2.6.24 would be a nice, but it won't be easy...
>
> Miklos
>
--
Thanks,
Steve
next prev parent reply other threads:[~2007-07-27 16:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 13:45 Miklos Szeredi
2007-07-27 14:10 ` Steve French
2007-07-27 14:20 ` Miklos Szeredi
2007-07-27 15:30 ` Ian Kent
2007-07-27 15:40 ` Miklos Szeredi
2007-07-27 16:04 ` Steve French [this message]
2007-07-27 16:09 ` Miklos Szeredi
2007-07-28 6:45 ` Ian Kent
2007-07-29 15:07 ` Jan Engelhardt
2007-07-27 19:43 ` Chuck Lever
2007-07-27 20:03 ` Miklos Szeredi
2007-07-27 20:12 ` Chuck Lever
2007-07-28 5:37 ` Miklos Szeredi
2007-07-30 15:20 ` Chuck Lever
2007-07-31 8:52 ` Miklos Szeredi
2007-07-31 14:19 ` Chuck Lever
2007-07-31 20:22 ` Miklos Szeredi
2007-07-31 21:16 ` Chuck Lever
2007-07-31 21:27 ` Trond Myklebust
2007-08-01 6:20 ` Miklos Szeredi
2007-07-31 22:21 ` Karel Zak
2007-08-01 6:52 ` Miklos Szeredi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=524f69650707270904j24038282le55f3981dff560a@mail.gmail.com \
--to=smfrench@gmail.com \
--cc=aia21@cantab.net \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bfennema@falcon.csc.calpoly.edu \
--cc=dhowells@redhat.com \
--cc=dushistov@mail.ru \
--cc=ericvh@gmail.com \
--cc=hirofumi@mail.parknet.co.jp \
--cc=holzheu@de.ibm.com \
--cc=hpa@zytor.com \
--cc=kurt.hackel@oracle.com \
--cc=kzak@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=mark.fasheh@oracle.com \
--cc=mhalcrow@us.ibm.com \
--cc=miklos@szeredi.hu \
--cc=mikulas@artax.karlin.mff.cuni.cz \
--cc=phillip@hellewell.homeip.net \
--cc=rathamahata@php4.ru \
--cc=raven@themaw.net \
--cc=reiserfs-devel@vger.kernel.org \
--cc=sfrench@samba.org \
--cc=shaggy@austin.ibm.com \
--cc=trond.myklebust@fys.uio.no \
--cc=vandrove@vc.cvut.cz \
--cc=wli@holomorphy.com \
--cc=xfs-masters@oss.sgi.com \
--cc=zippel@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®