From: seth vidal <skvidal@phy.duke.edu>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: hjl@users.sourceforge.net, nfs@lists.sourceforge.net
Subject: Re: NFSv4 daemons...
Date: Thu, 08 Jan 2004 22:41:59 -0500 [thread overview]
Message-ID: <1073619719.12271.7.camel@binkley> (raw)
In-Reply-To: <1073608448.1380.22.camel@nidelv.trondhjem.org>
On Thu, 2004-01-08 at 19:34, Trond Myklebust wrote:
> We're at the point now with the NFSv4 project that we'd like to publish
> the user daemons that are necessary to support the existing client in
> the 2.6.0 kernel.
>
> Would it make sense to add these to the existing nfs-utils package?
>
>
What type of stability have you seen from these?
Do you think these might be in a place to benefit from some wider use?
Thanks
-sv
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-01-09 3:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 0:34 NFSv4 daemons Trond Myklebust
2004-01-09 3:41 ` seth vidal [this message]
2004-01-09 4:06 ` Trond Myklebust
2004-01-09 17:09 ` Bogdan Costescu
2004-01-09 20:45 ` trond.myklebust
2004-01-23 14:54 ` Paul Jakma
2004-01-23 16:20 ` J. Bruce Fields
2004-01-24 3:41 ` Paul Jakma
2004-01-09 15:27 ` Steve Dickson
2004-01-09 21:05 ` William A.(Andy) Adamson
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=1073619719.12271.7.camel@binkley \
--to=skvidal@phy.duke.edu \
--cc=hjl@users.sourceforge.net \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.