public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian May <bam@snoopy.apana.org.au>
To: linux-kernel@vger.kernel.org
Subject: Re: problems with reiserfs + nfs using 2.4.2-pre4
Date: 21 Feb 2001 09:54:19 +1100	[thread overview]
Message-ID: <84ae7hge3o.fsf@snoopy.apana.org.au> (raw)
In-Reply-To: <E14V1Xa-0005Bf-00@the-village.bc.nu> <200102200211.f1K2BO002802@konerding.com>
In-Reply-To: dek_ml@konerding.com's message of "20 Feb 01 02:11:23 GMT"

>>>>> "dek" == dek ml <dek_ml@konerding.com> writes:

    dek> OK so I think what I can take from this is: for kernel 2.4 in
    dek> the foreseeable future, reiserfs over NFS won't work without
    dek> a special patch.  And, filesystems other than ext2 in general

Does this apply to the user space NFS server? kernel space NFS server?
Or both?
-- 
Brian May <bam@snoopy.apana.org.au>

  reply	other threads:[~2001-02-20 22:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-19  0:18 problems with reiserfs + nfs using 2.4.2-pre4 dek_ml
2001-02-19  0:37 ` Neil Brown
2001-02-19  2:56   ` dek_ml
2001-02-19  3:40     ` Neil Brown
2001-02-19 11:23       ` Alan Cox
2001-02-20  0:40         ` Neil Brown
2001-02-20  1:15           ` Chris Mason
2001-02-20  1:34             ` Neil Brown
2001-02-20  1:24           ` Alan Cox
2001-02-20  1:37             ` Neil Brown
2001-02-20  2:11             ` dek_ml
2001-02-20 22:54               ` Brian May [this message]
2001-02-20 23:30                 ` Chris Mason
2001-02-20  2:38           ` Roman Zippel
2001-02-20  9:44             ` [NFS] " Trond Myklebust
2001-02-20 14:02               ` Roman Zippel
2001-02-20 15:16                 ` Trond Myklebust
2001-02-20 16:26                   ` Roman Zippel
2001-02-21  3:02             ` Neil Brown
2001-02-21 12:43               ` [NFS] " Trond Myklebust
2001-02-19  1:55 ` Alan Cox
2001-02-19 15:37   ` Chris Mason

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=84ae7hge3o.fsf@snoopy.apana.org.au \
    --to=bam@snoopy.apana.org.au \
    --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