From: Christoph Hellwig <hch@infradead.org>
To: Neil Brown <neilb@suse.de>
Cc: nfs@lists.sourceforge.net
Subject: Re: [PATCH 00/17] RFC: proposed changes to the NFS mount command
Date: Mon, 16 Jul 2007 09:07:23 +0100 [thread overview]
Message-ID: <20070716080723.GA19783@infradead.org> (raw)
In-Reply-To: <18074.61070.150991.554588@notabene.brown>
On Mon, Jul 16, 2007 at 02:05:34PM +1000, Neil Brown wrote:
> I've wondered why that was happening... Can't we just make a version
> x+1 with a big string buffer so new options get put there is regular
> string format and old options stay the way they are?
>
> But I guess that - long term - it is better to be just like other
> filesystems.
Having anything but a plain string means the filesystem is a complete
oddball. And with the planned removal of smbfs nfs would be the only
oddball left.
> > option that will disable building nfsmount.c and nfs4mount.c, and
> > enable building a version of these files that will introduce support
> > for passing mount options as a string (that work is yet to be done).
>
> Does this mean that you cannot compile nfs-utils to support both old
> and new kernels? Is that really a good plan?
> What is the over-all migration strategy?
Making the different argument passing variants exclusive sounds like
a bad idea indeed.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-07-16 8:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 3:14 [PATCH 00/17] RFC: proposed changes to the NFS mount command Chuck Lever
2007-07-16 4:05 ` Neil Brown
2007-07-16 8:07 ` Christoph Hellwig [this message]
2007-07-16 15:07 ` Chuck Lever
2007-07-16 15:03 ` Chuck Lever
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=20070716080723.GA19783@infradead.org \
--to=hch@infradead.org \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.