From: michael chang <thenewme91@gmail.com>
To: David Masover <ninja@slaphack.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Distributions with out-of-the-box Reiser4 support?
Date: Wed, 10 Aug 2005 22:41:08 -0400 [thread overview]
Message-ID: <b14e81f005081019411bf1b3e8@mail.gmail.com> (raw)
In-Reply-To: <42FA9ADF.9050602@slaphack.com>
On 8/10/05, David Masover <ninja@slaphack.com> wrote:
> > So, to date, we have yet to see any recently released operating
> > systems with native out-of-the-box root Reiser4 support, it seems...
>
> Wasn't there something about yoper?
Yeah, there was, although someone discounted it for being a year old
release... [compared to Debian Sarge, that's pretty new...].
> > *sigh* Oh well... I guess we won't see it until we see it in vanilla
> > kernel and/or when the recompressor and/or resizer are ready... or
> > someone takes an initiative.
>
> If I was running a distro, I'd put big fat warnings around a non-default
> option for Reiser4, until the repacker was done. Then I'd make it the
This is what the Kernel Config does -- so no one will build with it
[they're scared it'll break something].
> default FS, and mark ext3 as "legacy" ;)
Then I'd have to modify the installer and the kernel now. And again
every time Reiser4 makes a major leap. [Not to mention I've yet to
see one person singlehandedly do a full distro -- a livecd /maybe/,
but probably not.] Logically, the maintainers will wait until
something is reasonably stable, and put it in when they're nice and
ready. *shrugs* Besides, how many of them are on a release cycle
anyways? But yeah, ext3 could be marked as legacy. That said, I'm
not going to go as far as to remove it from my kernel. [What if I want
to put my kernel on a ext2/3 boot partition?] ^^
--
~Mike
- Just my two cents
- No man is an island, and no man is unable.
next prev parent reply other threads:[~2005-08-11 2:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-10 16:48 Distributions with out-of-the-box Reiser4 support? Clemens Eisserer
2005-08-10 17:12 ` michael chang
2005-08-10 21:15 ` David Masover
2005-08-10 21:34 ` michael chang
2005-08-10 22:12 ` David Masover
2005-08-10 23:09 ` michael chang
2005-08-11 0:25 ` David Masover
2005-08-11 2:41 ` michael chang [this message]
2005-08-11 2:49 ` michael chang
2005-08-11 10:07 ` Nikita Danilov
2005-08-11 11:31 ` gimpel
2005-08-11 14:27 ` Clemens Eisserer
2005-08-11 17:30 ` gimpel
2005-08-12 2:51 ` Hans Reiser
2005-08-12 7:44 ` gimpel
[not found] <D63C0BE2D613C543B6F3305502E9784C2D1EDB@OCBEXS01001.rto.be>
2005-08-10 20:13 ` Clemens Eisserer
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=b14e81f005081019411bf1b3e8@mail.gmail.com \
--to=thenewme91@gmail.com \
--cc=ninja@slaphack.com \
--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.