From: Brian Tinsley <btinsley@emageon.com>
To: "Lever, Charles" <Charles.Lever@netapp.com>
Cc: Lorn Kay <lorn_kay@hotmail.com>,
nfs@lists.sourceforge.net, linux-ha@muc.de
Subject: Re: Re: NFS as a Cluster File System.
Date: Fri, 10 Jan 2003 09:23:38 -0600 [thread overview]
Message-ID: <3E1EE57A.5090003@emageon.com> (raw)
In-Reply-To: 6440EA1A6AA1D5118C6900902745938E07D551DF@black.eng.netapp.com
[-- Attachment #1: Type: text/plain, Size: 871 bytes --]
Lever, Charles wrote:
>>-----Original Message-----
>>From: Brian Tinsley [mailto:btinsley@emageon.com]
>>Sent: Thursday, January 09, 2003 4:11 PM
>>To: Lorn Kay
>>Cc: nfs@lists.sourceforge.net; linux-ha@muc.de
>>Subject: [NFS] Re: NFS as a Cluster File System.
>>
>>> Linux clients can use TCP instead of UDP.
>>>
>>>
>>Although I haven't had problems with this in our lab, I
>>believe the NFS authors still consider this experimental.
>>
>>
>
>the Linux NFS client support for TCP is not experimental.
>perhaps less mature than UDP, but definitely not experimental.
>
>the server, OTOH, sports brand new support for TCP. is that
>what you were referring to?
>
>
Yes, sorry to confuse the issue.
--
-[========================]-
-[ Brian Tinsley ]-
-[ Chief Systems Engineer ]-
-[ Emageon ]-
-[========================]-
[-- Attachment #2: Type: text/html, Size: 1554 bytes --]
next prev parent reply other threads:[~2003-01-10 15:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 14:51 Re: NFS as a Cluster File System Lever, Charles
2003-01-10 15:23 ` Brian Tinsley [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-14 16:01 Lever, Charles
2003-01-10 17:19 Lorn Kay
2003-01-12 21:29 ` Trond Myklebust
2003-01-09 23:13 Lorn Kay
2003-01-09 23:45 ` Donavan Pantke
2003-01-09 22:51 Lorn Kay
2003-01-10 15:01 ` Trond Myklebust
2003-01-10 17:38 ` Greg Lindahl
2003-01-12 21:23 ` Trond Myklebust
2003-01-09 19:39 Lorn Kay
2003-01-09 21:11 ` Brian Tinsley
2003-01-09 22:04 ` Brian Jackson
2003-01-09 23:02 ` Brian Tinsley
2003-01-09 21:29 ` Alan Robertson
2003-01-13 19:36 ` Neil Brown
2003-01-13 20:25 ` David B. Ritch
2003-01-13 20:40 ` Neil Brown
2003-01-13 20:50 ` David B. Ritch
2003-01-13 22:11 ` Neil Brown
2003-01-14 15:46 ` Trond Myklebust
2003-01-14 16:01 ` Kumaran Rajaram
2003-01-14 16:08 ` 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=3E1EE57A.5090003@emageon.com \
--to=btinsley@emageon.com \
--cc=Charles.Lever@netapp.com \
--cc=linux-ha@muc.de \
--cc=lorn_kay@hotmail.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.