All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Steffen Persvold <sp@scali.com>
Cc: <nfs@lists.sourceforge.net>,  <linux-kernel@vger.kernel.org>,
	<trond.myklebust@fys.uio.no>
Subject: Re: IRIX NFS server and Linux NFS client
Date: 11 Apr 2002 14:09:22 +0200	[thread overview]
Message-ID: <shs662yjv2l.fsf@charged.uio.no> (raw)
In-Reply-To: <Pine.LNX.4.30.0204111218440.30970-100000@elin.scali.no>

>>>>> " " == Steffen Persvold <sp@scali.com> writes:

     > I forgot to mention that NFSv3 works when an IRIX client mounts
     > the same directory (i.e the directory shows up as "nfs" and not
     > "nfs2" in the mount table on the IRIX client).

     > Could it be that IRIX only supports NFSv3 with TCP and not UDP
     > (I didn't try TCP mounting on the Linux client) ?

Have you applied

  http://www.fys.uio.no/~trondmy/src/2.4.18/linux-2.4.18-seekdir.dif

in order to work around the glibc-2.x readdir bugs?

Cheers,
  Trond

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

WARNING: multiple messages have this Message-ID (diff)
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Steffen Persvold <sp@scali.com>
Cc: <nfs@lists.sourceforge.net>, <linux-kernel@vger.kernel.org>,
	<trond.myklebust@fys.uio.no>
Subject: Re: IRIX NFS server and Linux NFS client
Date: 11 Apr 2002 14:09:22 +0200	[thread overview]
Message-ID: <shs662yjv2l.fsf@charged.uio.no> (raw)
In-Reply-To: <Pine.LNX.4.30.0204111218440.30970-100000@elin.scali.no>

>>>>> " " == Steffen Persvold <sp@scali.com> writes:

     > I forgot to mention that NFSv3 works when an IRIX client mounts
     > the same directory (i.e the directory shows up as "nfs" and not
     > "nfs2" in the mount table on the IRIX client).

     > Could it be that IRIX only supports NFSv3 with TCP and not UDP
     > (I didn't try TCP mounting on the Linux client) ?

Have you applied

  http://www.fys.uio.no/~trondmy/src/2.4.18/linux-2.4.18-seekdir.dif

in order to work around the glibc-2.x readdir bugs?

Cheers,
  Trond

  reply	other threads:[~2002-04-11 12:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <15540.60384.355250.346480@notabene.cse.unsw.edu.au>
2002-04-11  7:34 ` IRIX NFS server and Linux NFS client Steffen Persvold
2002-04-11 10:22   ` Steffen Persvold
2002-04-11 10:22     ` Steffen Persvold
2002-04-11 12:09     ` Trond Myklebust [this message]
2002-04-11 12:09       ` Trond Myklebust
2002-04-11 13:04     ` James Pearson
2002-04-11 13:19       ` Steffen Persvold
2002-04-11 18:13     ` Thomas Duffy
2002-04-12  3:22       ` Steffen Persvold
2002-04-12  3:44         ` Thomas Duffy
2002-04-11 12:10   ` Emanuel Quass

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=shs662yjv2l.fsf@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    --cc=sp@scali.com \
    /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.