From: Oleg Drokin <green@namesys.com>
To: Troy Wu <troy@sequence.stanford.edu>
Cc: ReiserFS at NameSys <reiserfs-list@namesys.com>,
NFS at SourceForge <NFS@lists.sourceforge.net>
Subject: Re: weird symlink problem persists...
Date: Tue, 17 Sep 2002 10:18:25 +0400 [thread overview]
Message-ID: <20020917101825.B30035@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.44L1.0209162228450.13963-100000@sequence.stanford.edu>
Hello!
On Mon, Sep 16, 2002 at 11:07:51PM -0700, Troy Wu wrote:
> I'm using the nfs-utils-1.0.1 tools on a 2.4.10 kernel (relatively stock
> SuSE-7.3 kernel) with ReiserFS 3.6.25 (but using the 3.5.x disk format).
Linux kernel version 2.4.10 (even patched by SuSE) is way out of date and
should not be used.
There are updated kernels available from SuSE right now to which yo should
upgrade. Pick at least 2.4.16 from SuSE updates or 2.4.18 if you choose to
switch to vanilla kernels.
Also right after kernel switch check your reiserfs filesystems with updated
reiserfsprogs to make sure there is no corruptions left from old kernels.
Bye,
Oleg
prev parent reply other threads:[~2002-09-17 6:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 6:07 weird symlink problem persists Troy Wu
2002-09-17 6:18 ` Oleg Drokin [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=20020917101825.B30035@namesys.com \
--to=green@namesys.com \
--cc=NFS@lists.sourceforge.net \
--cc=reiserfs-list@namesys.com \
--cc=troy@sequence.stanford.edu \
/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.