From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Siim Vahtre <siim@pld.ttu.ee>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
linux-kernel@vger.kernel.org
Subject: Re: nfs issues
Date: Sun, 6 Apr 2003 17:02:13 +0200 [thread overview]
Message-ID: <16016.16757.380048.996214@charged.uio.no> (raw)
In-Reply-To: <Pine.GSO.4.53.0304061731540.17774@pitsa.pld.ttu.ee>
>>>>> " " == Siim Vahtre <siim@pld.ttu.ee> writes:
> Using 2.4 kernel for client is fine. (tried 2.4.21-pre7
> aswell). But I want to use 2.5 on the client side.. atm it
> screws the data.
Tough. 2.5.x is a development kernel, and yes, there are still bugs
and issues to be tracked down.
If you need stability use 2.4.x
Cheers,
Trond
next prev parent reply other threads:[~2003-04-06 14:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-06 6:51 Siim Vahtre
2003-04-06 12:54 ` Trond Myklebust
2003-04-06 14:33 ` Siim Vahtre
2003-04-06 15:02 ` Trond Myklebust [this message]
2003-04-06 15:04 ` Siim Vahtre
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=16016.16757.380048.996214@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=siim@pld.ttu.ee \
/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
all inboxes | Powered by JetHome®