From: Nikita Danilov <Nikita@Namesys.COM>
To: "P.Agenbag" <internet@psimation.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.13 kernel and ext3???
Date: Tue, 30 Oct 2001 21:07:52 +0300 [thread overview]
Message-ID: <15326.60536.561925.749776@beta.reiserfs.com> (raw)
In-Reply-To: <3BDEE870.1060104@psimation.com>
In-Reply-To: <3BDEE870.1060104@psimation.com>
P.Agenbag writes:
> Hi
> I just installed RedHat 7.2 with the 2.4.7 kernel. Low and behold, when
> I tried to install the latest kernels, I see that there are many options
> in the RedHat 2.4.7 kernel that are not even in the 2.4.13 kernel! How
> does this work? Also, I see many (EXPERIMENTAL) greyd-out areas in the
> kernel as well as other greyd out areas which are not experimental, yet
> won't allow me to select it ( reiserfs for example ) .
> How can I get reiserfs to compile into the kernel, and to satsify my
> curiosity, how do you enable the experimental options?
Turn on first option "Prompt for development and/or incomplete
code/drivers" in the first configuration sub-menu "Code maturity level
options".
Read namesys.com/faq.html
>
> Does it mean that if there is a fairly large difference between the
> RedHat 2.4.7 and the stock one from kernel.org, that they are not really
> the same? ie, does anyone foresee any future problems with redhat adding
> all these extra features to their kernel and people who would like to
> upgrade to a newer version ( for one, I selected ext3 during install,
> yet, now trying to install 2.4.13, I must revert back to ext2...)
>
> Thanks
Nikita.
>
>
next prev parent reply other threads:[~2001-10-30 18:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-30 17:50 2.4.13 kernel and ext3??? P.Agenbag
2001-10-30 18:07 ` Nikita Danilov [this message]
2001-10-30 18:08 ` Rik van Riel
2001-10-30 23:07 ` Alan Cox
2001-10-30 18:15 ` Joel Jaeggli
2001-10-30 22:57 ` Alessandro Suardi
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=15326.60536.561925.749776@beta.reiserfs.com \
--to=nikita@namesys.com \
--cc=internet@psimation.com \
--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