From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: retiring device.map
Date: Tue, 6 May 2008 17:18:00 +0200 [thread overview]
Message-ID: <20080506151800.GA25697@thorin> (raw)
In-Reply-To: <1208773866.29071.11.camel@dv>
On Mon, Apr 21, 2008 at 06:31:06AM -0400, Pavel Roskin wrote:
>
> I would explore the possibility of retiring device.map completely or
> limiting its use to some rare cases.
>
> In the vast majority of cases, the installer should not rely on knowing
> the BIOS numbers of the devices involved in the boot process. BIOS
> provides the boot drive, which should generally be trusted. The
> installer only needs to know whether the media is a hard drive to enable
> a workaround for buggy BIOSes providing a wrong boot drive.
>
> I'm not sure about EFI and Open firmware, but I think the situation is
> similar. There should be enough information to find the boot drive at
> the boot time without requiring any guesswork in the installer.
>
> We may need to tell GRUB what device to use to look for additional files
> when the boot process involves more than one drive. But even then, I'd
> rather prefer that GRUB uses labels, not hardcoded BIOS numbers.
I completely agree. How do we go about this? First of all we need support
for labels, right?
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call… if you are unable to speak?
(as seen on /.)
next prev parent reply other threads:[~2008-05-06 15:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4807AA02.1020909@mail.berlios.de>
[not found] ` <20080418132858.GH29226@thorin>
2008-04-19 14:34 ` grub-probe fails during grub2 update (Debian) Stefan Weil
2008-04-20 10:07 ` Robert Millan
2008-04-21 10:31 ` Pavel Roskin
2008-05-06 15:18 ` Robert Millan [this message]
2008-05-06 15:43 ` retiring device.map Pavel Roskin
2008-05-07 13:03 ` Robert Millan
2008-05-07 17:22 ` Pavel Roskin
2008-05-07 17:39 ` Bean
2008-05-08 17:08 ` Colin D Bennett
2008-05-09 12:51 ` Robert Millan
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=20080506151800.GA25697@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.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 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.