From: Steve Dickson <SteveD@redhat.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: nfs@lists.sourceforge.net
Subject: Re: [kNFSD] [PATCH] fixed '-p port' arg to rpc.nfsd plus more.
Date: Tue, 22 Mar 2005 05:17:21 -0500 [thread overview]
Message-ID: <423FF0B1.8060007@RedHat.com> (raw)
In-Reply-To: <16959.23048.930497.833801@cse.unsw.edu.au>
Neil Brown wrote:
> I'm happy to consider changes in syntax, but I really don't like
> merging these very different concepts in the one file.
My initial thought is this adds much more complexity that
really needed... All that's needed is to set the port, version
and protocol. As soon as you added in address and address types,
it adds a hole new level complexity that may not be needed,
to solve this particular problem.
but let me take a closer took to see how much is truly need to
create a couple more proc files and well as the parsing
routines to handle theses type of syntaxes....
steved.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-03-22 10:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-21 14:42 [kNFSD] [PATCH] fixed '-p port' arg to rpc.nfsd plus more Steve Dickson
2005-03-21 14:56 ` J. Bruce Fields
2005-03-21 15:18 ` Trond Myklebust
2005-03-21 15:59 ` Steve Dickson
2005-03-21 15:46 ` [KNFSD] " Chip Salzenberg
2005-03-21 16:22 ` Steve Dickson
2005-03-21 16:39 ` Chip Salzenberg
2005-03-21 23:34 ` [kNFSD] " Neil Brown
2005-03-22 10:17 ` Steve Dickson [this message]
2005-03-22 12:27 ` Steve Dickson
2005-03-22 13:10 ` Steve Dickson
2005-03-22 15:01 ` Steve Dickson
2005-03-23 11:56 ` Steve Dickson
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=423FF0B1.8060007@RedHat.com \
--to=steved@redhat.com \
--cc=neilb@cse.unsw.edu.au \
--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