public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <warnera6@egr.msu.edu>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: grub reiser4
Date: Sun, 02 Oct 2005 12:04:01 -0400	[thread overview]
Message-ID: <434004F1.1000404@egr.msu.edu> (raw)
In-Reply-To: <623652d50510020302t7211c5e2g@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chris Bainbridge wrote:
> On 02/10/05, R Hill <dirtyepic.sk@gmail.com> wrote:
> 
>>The grub maintainer's stance was that reiser 4 support would not be
>>included in grub until it was included in gentoo-sources, not any kernel
>>in portage.  The grub maintainer has been AWOL for the last 9 months or
>>so however, so i guess it's now up to the base-system herd.  I was under
>>the impression that feature-adding patches should be sent upstream.
>>
>>I still think it's retarded to have a reiser 4 boot partition, but
>>whatever stirs your pot. ;P
> 
> 
> It makes sense if you're actually using reiser4 for everything else.
> Why bloat your kernel with an extra FS just for /boot?
> 

Because most people want a tried and true fs on /boot, because if that
tanks your system doesn't boot.  I'm not trying to bash reiser here, I
still use ext2 on /boot even if xfs is my main fs of choice for this reason.

Alec Warner (antarus)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iQIVAwUBQ0AE8WzglR5RwbyYAQK8qg//ZkvUesz1inYyajZmR5f0AaghEa77cT+m
bzZquMF9ttZj81lyqY9dgMvMVCa6+xVU+ZYx7Z76sbDeNeAmn5gQ3vW4KksHulVB
pv7SH49hgzKA/ThTjSZsDeVbSVfnAjnElC17keXOp3i7AzPN2QoefqsaheW+L9mg
f9Pb63Lz73e49Ahj9YmERJ37HZY28xPIWorlqlL+XkpOhymcofgU9o5iC6qrz+vi
ht9cs7E4zNjU1JdNQ8ydsfz6z6Qd/YAu3M+zsd8ENOzO/0iIHFTI3l6Xss3ZfH0b
bH4OdLni6qch/dWzoz2WqUo+JQgRYvwnDbE0wtr5kVSkhkmwRG9JFTY5zxzqtbTd
MP/QGdx+j79muwVtI4Dl6h4GjnZtRlVmgSjFnNxMwFarITIoqJEtoFgP+mPXxEhe
pPC9UwpphOujwMf8K9A6+a54KmGgH+SKKCcDMkiAFNje3HdvKcZTaDeXMzLODMBa
iAyfewvzUIZG59AH0uN00sfwQ0lWiISA5p8ILVuoHFsajobv+nvUiWDBq2xZr0NU
geHBJ6LsUjHbBSGFiMpWnP49uZCHv2PCbBxhHGIGY007fC1lVoiidah51iLZ3rid
3aU+KCuuXDj3IX4n2uG2HRJZHp8sRLUaCdOWR6oH4+EkRIcF5eCuYTSqN6H1Edrv
v1YbLXiDjS4=
=DXSo
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list



  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
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 [this message]
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=434004F1.1000404@egr.msu.edu \
    --to=warnera6@egr.msu.edu \
    --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