From: "Henning P. Schmiedehausen" <hps@tanstaafl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: TESTERS PLEASE - improvements to knfsd for 2.4.2
Date: Thu, 22 Feb 2001 14:24:04 +0000 (UTC) [thread overview]
Message-ID: <9737e4$o35$1@forge.intermeta.de> (raw)
In-Reply-To: <14996.37528.486223.118752@notabene.cse.unsw.edu.au>
neilb@cse.unsw.edu.au (Neil Brown) writes:
> I am looking forward to seeing lots of downloads and absolutely no
> problem reports.... but is seems unlikely.
> Alan Cox has suggested that these changes may not be appropriate for
> 2.4, so we might have to wait for 2.5 to see them on kernel.org, but
> we don't have to wait till then to find the bugs.
Oh, please not again a stable kernel series with NFS problems, we're
locked in for ages. 2.2 was bad enough up to 2.2.18. We have ReiserFS
in 2.4.1 (and not in 2.4.0), could we _please_ get NFS-exportable
ReiserFS in 2.4.4 or 2.4.5?
Yes, will test. :-) Though I won't touch any 2.4 release in production
up to at least 2.4.5 (first really usable 2.0 was around this, first
2.2 too. =:-)
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
D-91054 Buckenhof Fax.: 09131 / 50654-20
next prev parent reply other threads:[~2001-02-22 14:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-22 4:16 TESTERS PLEASE - improvements to knfsd for 2.4.2 Neil Brown
2001-02-22 14:24 ` Henning P. Schmiedehausen [this message]
2001-02-23 17:53 ` Matthias Andree
2001-02-23 18:35 ` Alan Cox
2001-02-25 17:06 ` Matthias Andree
2001-02-23 20:04 ` james rich
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='9737e4$o35$1@forge.intermeta.de' \
--to=hps@tanstaafl.de \
--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 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.