From: "Yury V. Umanets" <umka@namesys.com>
To: Hans Reiser <reiser@namesys.com>
Cc: jedi@ninja.dynup.net, reiserfs-list@namesys.com
Subject: Re: [jedi@ninja.dynup.net: Re: V4 status]
Date: Fri, 05 Dec 2003 15:56:27 +0300 [thread overview]
Message-ID: <1070628987.945.3.camel@firefly> (raw)
In-Reply-To: <3FD07ECB.2080004@namesys.com>
On Fri, 2003-12-05 at 15:49, Hans Reiser wrote:
> >
> >
> >> and v3 was never supported very well).
> >>
> >>
> >I thought, that it is supported good enough :) Can you be more specific
> >on this?
> >
> >
> >
> >
> SuSE users use grub and reiserfs by default.
Yep. Speaking about reiserfs support more specifically, I can say, that
GRUB supports reiserfs 3.5-3.6 and with relocated journal in both modes:
with using stage_1.5 and without using it. Using stage 1_5 means, that
GRUB is able to read kernel image from reiserfs even if it was fully of
tails (like it is possible in reiser4).
--
umka
prev parent reply other threads:[~2003-12-05 12:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031205085814.GD1926@backtop.namesys.com>
2003-12-05 9:20 ` [jedi@ninja.dynup.net: Re: V4 status] Yury V. Umanets
2003-12-05 12:49 ` Hans Reiser
2003-12-05 12:56 ` Yury V. Umanets [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=1070628987.945.3.camel@firefly \
--to=umka@namesys.com \
--cc=jedi@ninja.dynup.net \
--cc=reiser@namesys.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.