From: "H . J . Lu" <hjl@gnu.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Chris Jensen <dr_spirograph@technologist.com>,
NFS maillist <nfs@lists.sourceforge.net>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [NFS] New files on read only NFS mount
Date: Wed, 14 Mar 2001 23:09:32 -0800 [thread overview]
Message-ID: <20010314230932.A29059@gnu.org> (raw)
In-Reply-To: <001a01c0aac0$80432260$0100a8c0@chris> <shs8zmbksxo.fsf@charged.uio.no> <001601c0ab02$df976860$0100a8c0@chris> <15020.58260.471102.944034@charged.uio.no>
In-Reply-To: <15020.58260.471102.944034@charged.uio.no>; from trond.myklebust@fys.uio.no on Mon, Mar 12, 2001 at 03:56:20PM +0100
On Mon, Mar 12, 2001 at 03:56:20PM +0100, Trond Myklebust wrote:
> >>>>> " " == Chris Jensen <christopher.jensen@studentmail.newcastle.edu.au> writes:
>
> >> Details please, the minimum info required being 'which kernel
> >> is your client running'?
> >>
>
> > Oh yeah, whoops, sorry The server is a 586 and the client is
> > 686. They're both using nfs-utils 0.2.1, under linux 2.4.0
> > with NFS v3 enabled, with glibc 2.2.1 The pertinent line in
> > /etc/exports is / 192.168.0.1(rw,no_root_squash)
>
> How does the following patch work out?
>
I can duplicate the problem and this patch fixes it.
Thanks.
H.J.
prev parent reply other threads:[~2001-03-15 7:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001a01c0aac0$80432260$0100a8c0@chris>
[not found] ` <shs8zmbksxo.fsf@charged.uio.no>
[not found] ` <001601c0ab02$df976860$0100a8c0@chris>
2001-03-12 14:56 ` [NFS] New files on read only NFS mount Trond Myklebust
2001-03-15 7:09 ` H . J . Lu [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=20010314230932.A29059@gnu.org \
--to=hjl@gnu.org \
--cc=dr_spirograph@technologist.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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