From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Using "root=LABEL=xxxx" in grub.conf
Date: Mon, 9 Feb 2009 19:54:25 +0200 [thread overview]
Message-ID: <200902091954.25601.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <116687D8-1C3D-4653-B34F-B7F218AE3D12@stellar.eclipse.co.uk>
On Monday 09 February 2009 18:51:24 Stroller wrote:
> On 9 Feb 2009, at 10:32, Michael Hampicke wrote:
> >>> It would appear that you need an initrd/initramfs to use this.
> >>
> >> Ah! Many thanks. I will live without this shortcut, then, I think.
> >
> > If you, like me, prefere to compile your own kernel, there's still an
> > easy way to create a initrd for your kernel: with genkernel
> > I use this command to compile my pre-configured kernel
> >
> > genkernel --no-clean --no-mrproper \
> > --makeopts=-j2 --loglevel=5 --install --symlink all
> >
> > To include support for disk labels use the switch --disklabel
>
> I am resistant to the idea of using an initrd, because IIRC it's an
> extra file that has to be stored in /boot, creating extra "clutter" in
> there.
>
> I'm kinda thinking that using the label prevents failed boots in the
> event that the drives are recognised in a different order in the
> future, but nevertheless I don't "like" initrd and the longer kernel
> lines in grub.conf that they require.
>
> I appreciate this is somewhat irrational.
Not really.
initrds are there for two cases, and only two cases: 1) a generic boot process
for precompiled binary distros where the maintainers has no idea what the
user has and must support all combinations for all possible users. 2) Boot
scenarios where you require access to the root device before you have access
to the root device (/ on lvm, boot off some raid setups, etc)
The first does not apply to gentoo at all. If you don't have the second,
initrd is just extra unnecessary clutter and complexity and you are quite
correct to resist it's presence.
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2009-02-09 17:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c3yKO-8r8-13@gated-at.bofh.it>
[not found] ` <c3Atc-2Vu-23@gated-at.bofh.it>
[not found] ` <c3ACW-39s-7@gated-at.bofh.it>
2009-02-09 10:32 ` [gentoo-user] Using "root=LABEL=xxxx" in grub.conf Michael Hampicke
2009-02-09 16:51 ` Stroller
2009-02-09 17:54 ` Alan McKinnon [this message]
2009-02-09 18:03 ` Dirk Heinrichs
2009-02-09 22:26 ` Stroller
2009-02-10 17:59 ` Dirk Heinrichs
2009-02-10 18:46 ` Mick
2009-02-10 20:11 ` Albert Hopkins
2009-02-09 7:26 Stroller
2009-02-09 7:42 ` Dale
2009-02-09 7:56 ` Stroller
2009-02-09 8:02 ` Dale
2009-02-09 9:04 ` Stroller
2009-02-09 8:03 ` Stroller
2009-02-09 8:10 ` Dale
2009-02-09 9:18 ` Neil Bothwick
2009-02-09 9:28 ` Stroller
2009-02-09 9:41 ` Neil Bothwick
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=200902091954.25601.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@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