public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: 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: Sat, 28 Jul 2007 14:45:59 +0800	[thread overview]
Message-ID: <1185605159.8326.5.camel@raven.themaw.net> (raw)
In-Reply-To: <E1IERvH-00016M-00@dorka.pomaz.szeredi.hu>

On Fri, 2007-07-27 at 17:40 +0200, Miklos Szeredi 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.

Oh .. sorry, I wasn't paying enough attention.

But now might be a good time to propose the removal of autofs and rename
autofs4 to autofs. I would need to provide some way to map autofs4
module load requests to autofs for backward compatibility but haven't
thought about that yet.

> 
> 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...

The autofs4 (and, if needed autofs) should be straight forward.
I'll do these.

Ian



  parent reply	other threads:[~2007-07-28  6:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-27 13:45 request for patches: showing mount options 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
2007-07-27 16:09       ` Miklos Szeredi
2007-07-28  6:45     ` Ian Kent [this message]
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=1185605159.8326.5.camel@raven.themaw.net \
    --to=raven@themaw.net \
    --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=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