From: Oleg Drokin <green@namesys.com>
To: Scott Bragg <jsbragg@pacific.net.au>
Cc: ReiserFS Mailing List <reiserfs-list@namesys.com>
Subject: Re: How not to liquidate a company... (Upgrading from 2.2.x kernel (patched) to 2.4.x. [and testimonial])
Date: Thu, 20 Jun 2002 09:09:06 +0400 [thread overview]
Message-ID: <20020620090906.A4279@namesys.com> (raw)
In-Reply-To: <IOELIGOBLCIAGKOJFKMBAECDCAAA.jsbragg@pacific.net.au>
Hello!
On Wed, Jun 19, 2002 at 11:58:14PM -0700, Scott Bragg wrote:
> I'd like to install a newer distribution on the system, but am not sure if
> there is an issue when switching from a system using a 2.2.16 kernel patched
> with ReiserFS to a 2.4.18 kernel.
Read Documentation/Changes from your 2.4.18 linux kernel source tree
to find out what utils should be upgraded to what versions, if you
are upgrading from 2.2.16 kernel.
> So, I have to install Linux on a new system disk, and would like to use
> Mandrake 8.1 (as I run this version on 12 systems I currently manage). So..
> can I just install Mandrake 8.1 and set up the 750Gb volume in fstab with
> reiserfs, or will it not be that simple?
If you are installing new system, then you have nothing to worry about.
Just make sure you run 2.4.18+ kernel (needed for reisergfs stability)
and also have reiserfsprogs-3.x.1b version of reiserfsprogs (Mandrake
seems to ship somewhat outdated version of these, so you'd need to upgrade this
component)
Bye,
Oleg
prev parent reply other threads:[~2002-06-20 5:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 6:58 How not to liquidate a company... (Upgrading from 2.2.x kernel (patched) to 2.4.x. [and testimonial]) Scott Bragg
2002-06-20 5:09 ` 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=20020620090906.A4279@namesys.com \
--to=green@namesys.com \
--cc=jsbragg@pacific.net.au \
--cc=reiserfs-list@namesys.com \
/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.