From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Disk Labels in Handbook
Date: Thu, 10 Feb 2011 15:39:21 +0000 [thread overview]
Message-ID: <52E9D367-D66A-477C-8F12-20F7A6B55E38@stellar.eclipse.co.uk> (raw)
In-Reply-To: <AANLkTikzyucjmhoRNOjMOvNXUpUQsqP-7gYxdsC56DzK@mail.gmail.com>
On 9/2/2011, at 2:27pm, Mark Knecht wrote:
> ...
> Following Walt's recent thread about his experiences using grub2 I
> think getting folks used to disk labels at installation time, be they
> names or even better UUID's, might fit in very well with installation
> instructions that cover using grub2 instead of grub as a boot loader.
IMO this is what makes the problem a little less tractable.
Labels in /etc/fstab are nice, and they may ensure your disks are mounted correctly if the ordering changes. But the ordering might lead GRUB to be looking on the wrong disk for the kernel, and in that case labels in /etc/fstab alone don't help.
AIUI GRUB2 isn't yet marked stable. I think I read that GRUB2 is 150MB or so, and contains support for jpegs and whatnot - that's not really what I want in a bootloader.
At present use of /dev/sda1 &c in the handbook is very consistent.
Stroller.
next prev parent reply other threads:[~2011-02-10 15:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 13:51 [gentoo-user] Disk Labels in Handbook James
2011-02-09 14:16 ` Dale
2011-02-09 14:27 ` Mark Knecht
2011-02-09 20:58 ` Alan McKinnon
2011-02-10 10:00 ` Petri Rosenström
[not found] ` <20110210120055.6e7288c2@digimed.co.uk>
2011-02-10 12:31 ` Dale
2011-02-10 12:39 ` Joost Roeleveld
2011-02-10 12:45 ` Dale
2011-02-10 12:53 ` Joost Roeleveld
2011-02-10 12:56 ` Neil Bothwick
2011-02-10 13:14 ` Dale
2011-02-10 15:39 ` Stroller [this message]
2011-02-09 16:16 ` Jarry
2011-02-09 18:41 ` [gentoo-user] Re: Bug#354229 " James
2011-02-09 20:08 ` [gentoo-user] " Neil Bothwick
2011-02-10 15:17 ` [gentoo-user] " James
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=52E9D367-D66A-477C-8F12-20F7A6B55E38@stellar.eclipse.co.uk \
--to=stroller@stellar.eclipse.co.uk \
--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