From: Scott McDermott <mcdermot@questra.com>
To: nfs@lists.sourceforge.net
Subject: Re: current Trond NFS patch for 2.2.22?
Date: Mon, 7 Oct 2002 21:38:43 -0400 [thread overview]
Message-ID: <20021007213843.M26432@questra.com> (raw)
In-Reply-To: <shsfzvhsszs.fsf@charged.uio.no>; from trond.myklebust@fys.uio.no on Tue, Oct 08, 2002 at 01:56:39AM +0200
Trond Myklebust on Tue 8/10 01:56 +0200:
> >>>>> " " == Scott McDermott <mcdermot@questra.com> writes:
what's this empty string? where does it get its value? my MUA set up
improperly or something?
> > yes some of us are still using 2.2 if I use 2.2.22 + Trond's
> > linux-2.2.21-NFS.dif am I current? It applies fine (minus a
> > cast which was already included)
>
> Hardly current, but definitely up to the limits of which I'm prepared
> to go with 2.2.x 8-)
biggest thing stopping me from upgrading the servers to 2.4 is knowing
that everyone will get stale handles, this will be very hard to manage
logistically, too many disparate political units with clients mounting
off it. You said before that there is server code to handle old 2.2
cookies but I've heard otherwise from posts on the list and 2.2 works
too well for us right now to risk this. I really should get around to
testing this though. Truth is, 2.2 works well for our needs, I don't
really care to upgrade until we get something worthwhile like RPCSEC and
ACL support.
your patches affect client only though right?
Our servers are running 2.2.18pre19 with UDP rsize fix since forever,
with no problems whatever.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-10-08 1:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 22:37 current Trond NFS patch for 2.2.22? Scott McDermott
2002-10-07 23:56 ` Trond Myklebust
2002-10-08 1:38 ` Scott McDermott [this message]
2002-10-08 1:56 ` Trond Myklebust
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=20021007213843.M26432@questra.com \
--to=mcdermot@questra.com \
--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.