From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] grub reiser4
Date: Mon, 03 Oct 2005 09:17:10 -0400 [thread overview]
Message-ID: <1128345431.6692.29.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <623652d50510030210v222bf4b6q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2099 bytes --]
On Mon, 2005-10-03 at 10:10 +0100, Chris Bainbridge wrote:
> On 03/10/05, Mike Doty <kingtaco@gentoo.org> wrote:
> > I'd prefer if the patch was left out for amd64 users, or included via a
> > use flag. reiser4 isn't yet stable or proven on amd64.
>
> A quick search found this quote: "The topic in channel #gentoo-amd64
> on irc.freenode.net has said "Reiser4 is evil" for more than a year."
>
> However http://gentoo-wiki.com/HOWTO_AMD_64 and the forum threads it
> links to seem to suggest that people are successfully using reiser4 on
> amd64 with recent kernels?
The gentoo-wiki.com site is not an official Gentoo site. Anything
written there can't be considered factual or accurate, and definitely
doesn't reflect on official Gentoo stance on anything, except where
quoted directly from a gentoo.org site (other than the forums, and
probably not planet or universe, either). That being said, it's usually
correct on things. The forums has had reports of people using reiser4
on everything from their amd64 to their toaster forever, all claiming
"stability" even at times when reiser4 support wouldn't compile on that
platform. What I am trying to point out here is that reports in the
forums should be taken with a grain of salt. I'm unaware of any testing
having been done by the amd64 team recently. I am aware of several
people with "stable" reiser4 systems having the file system go tits up
on them, however. I don't remember what platform they were on, but I
also know that they were running kernels not in the tree, which means
they have questionable stability themselves, so pinpointing the file
system as the actual problem is difficult, at best. My suggestion is to
try it. If it works for you, then great. If it doesn't, don't come
asking us, as we'll probably say something like "I told you so."
Basically, I think it is perfectly fine to play around with reiser4, but
I wouldn't trust it with *my* data. Not yet.
--
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2011-10-31 3:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 18:10 [gentoo-dev] grub reiser4 Chris Bainbridge
2005-09-29 18:32 ` Mike Frysinger
2005-10-03 3:57 ` Mike Doty
2005-10-03 9:10 ` Chris Bainbridge
2005-10-03 12:47 ` Luis Medinas
2005-10-03 13:17 ` Chris Gianelloni [this message]
2005-10-05 11:13 ` Roy Marples
2005-10-03 13:09 ` Chris Gianelloni
2005-09-29 18:38 ` Bjarke Istrup Pedersen
2005-10-02 3:50 ` [gentoo-dev] " R Hill
2005-10-02 10:02 ` Chris Bainbridge
2005-10-02 16:04 ` Alec Warner
2005-10-02 16:38 ` Chris Bainbridge
2005-10-02 17:19 ` Dan Meltzer
2005-10-02 17:43 ` Chris Bainbridge
2005-10-02 23:51 ` [gentoo-dev] " Duncan
2005-10-03 12:57 ` [gentoo-dev] " Chris Gianelloni
2005-10-03 12:54 ` Chris Gianelloni
2005-10-03 13:43 ` [gentoo-dev] " Duncan
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=1128345431.6692.29.camel@cgianelloni.nuvox.net \
--to=wolf31o2@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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