From: Mogens Kjaer <mk@crc.dk>
To: linux-kernel@vger.kernel.org
Subject: Re: nfs client problem in kernel 2.4.0
Date: Wed, 17 Jan 2001 07:53:16 +0100 [thread overview]
Message-ID: <3A65415C.5A0D57F@crc.dk> (raw)
In-Reply-To: <3A6466E3.AB55716@crc.dk> <shsy9wb334a.fsf@charged.uio.no>
Trond Myklebust wrote:
> I'll bet it's the lseek that's screwing things up again. IIRC IRIX has
> an export option to cause it to generate 32-bit readdir cookies. Could
> you please try enabling it?
Sorry, I forgot to mention this: This option was already enabled.
Mogens
--
Mogens Kjaer, Carlsberg Laboratory, Dept. of Chemistry
Gamle Carlsberg Vej 10, DK-2500 Valby, Denmark
Phone: +45 33 27 53 25, Fax: +45 33 27 47 08
Email: mk@crc.dk Homepage: http://www.crc.dk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-17 6:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-16 15:21 nfs client problem in kernel 2.4.0 Mogens Kjaer
2001-01-16 15:53 ` Trond Myklebust
2001-01-16 16:04 ` Trond Myklebust
2001-01-18 12:32 ` Mogens Kjaer
2001-01-18 16:10 ` Trond Myklebust
2001-01-18 16:52 ` Mogens Kjaer
2001-01-17 6:53 ` Mogens Kjaer [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=3A65415C.5A0D57F@crc.dk \
--to=mk@crc.dk \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox