From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Scott McDermott <mcdermot@questra.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: current Trond NFS patch for 2.2.22?
Date: 08 Oct 2002 03:56:26 +0200 [thread overview]
Message-ID: <shs65wd7kxh.fsf@charged.uio.no> (raw)
In-Reply-To: <20021007213843.M26432@questra.com>
>>>>> " " == Scott McDermott <mcdermot@questra.com> writes:
> 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?
Nah. Xemacs wants to play games when formatting. I just hate having
the thing indent with
Scott McDermott> blah...
> 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.
Nobody is forcing you to upgrade, however I wanted to make the point
that 2.2.x is a 'critical fixes only' kernel. Otherwise I'm not
touching it...
Cheers,
Trond
-------------------------------------------------------
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
prev parent reply other threads:[~2002-10-08 1:56 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
2002-10-08 1:56 ` Trond Myklebust [this message]
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=shs65wd7kxh.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=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.