From: Amit Gud <agud@redhat.com>
To: Trond.Myklebust@netapp.com, neilb@suse.de
Cc: linux-fsdevel@vger.kernel.org, nfs@lists.sourceforge.net,
Steve Dickson <SteveD@redhat.com>
Subject: NFS mount redesign
Date: Tue, 27 Jun 2006 13:38:08 -0400 [thread overview]
Message-ID: <44A16D00.5050600@redhat.com> (raw)
I'm starting out with changing the mount interface for NFS from binary
to ASCII, preserving the backward-compatibility. The reason being it
would become more flexible to change the options.
Any counter-views, opinions, inputs?
Best,
AG
--
May the source be with you.
http://www.cis.ksu.edu/~gud
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
reply other threads:[~2006-06-27 17:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=44A16D00.5050600@redhat.com \
--to=agud@redhat.com \
--cc=SteveD@redhat.com \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-fsdevel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).