From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Next release?
Date: Mon, 21 Jul 2008 16:48:33 -0400 [thread overview]
Message-ID: <1216673313.11291.24.camel@dv> (raw)
In-Reply-To: <200807192216.23882.okuji@enbug.org>
On Sat, 2008-07-19 at 22:16 +0200, Yoshinori K. Okuji wrote:
> I am totally against ripping off device.map. Pavel's idea is too
> idealistic,
> and that regresses the flexibility.
Actually, it could be said that having device.map regresses flexibility.
Suppose I want to install GRUB on a flash drive that is seen
as /dev/sdb. I need to add /dev/sdb to device.map even though I'm not
going to see that flash drive again. I also need to check the options
to ensure that everything is installed on the flash drive and nothing is
installed elsewhere.
Suppose that we don't have device.map. Then I don't need to add entries
for temporary devices. Also, I won't be able to create a cross-drive
configuration by accident, simple because it won't be allowed by
default.
If you think that device.map is beneficial for cross-device installs,
then we can have an option to enable cross-device installs, that would
also enable device.map. Single-drive installs don't need to make any
assumptions about the BIOS numbers, and thus won't use device.map in any
way.
Actually, I think that even cross-device installs should rely on probing
the relevant drives rather than on cached information. But we can
discuss and implement it separately.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-07-21 20:48 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 13:03 Next release? Pavel Roskin
2008-07-14 16:55 ` Christian Franke
2008-07-14 20:27 ` Pavel Roskin
2008-07-15 5:40 ` Christian Franke
2008-07-20 21:10 ` Christian Franke
2008-07-15 13:49 ` Robert Millan
2008-07-15 15:07 ` Patrick Georgi
2008-07-15 18:39 ` Christian Franke
2008-07-15 18:32 ` Christian Franke
2008-07-15 21:04 ` Yoshinori K. Okuji
2008-07-15 22:31 ` Pavel Roskin
2008-07-15 23:15 ` Yoshinori K. Okuji
2008-07-15 23:21 ` Pavel Roskin
2008-07-15 23:32 ` Yoshinori K. Okuji
2008-07-15 23:52 ` Pavel Roskin
2008-07-16 14:11 ` Colin D Bennett
2008-07-16 14:17 ` Javier Martín
2008-07-16 16:17 ` Pavel Roskin
2008-07-16 16:28 ` Javier Martín
2008-07-16 16:08 ` Pavel Roskin
2008-07-19 15:14 ` device.map (Re: Next release?) Robert Millan
2008-07-21 21:26 ` Pavel Roskin
2008-07-22 21:36 ` Robert Millan
2008-07-22 21:57 ` Pavel Roskin
2008-07-22 22:08 ` Robert Millan
2008-07-22 22:46 ` Pavel Roskin
2008-07-19 15:06 ` Next release? Robert Millan
2008-07-19 20:16 ` Yoshinori K. Okuji
2008-07-19 20:59 ` Robert Millan
2008-07-21 20:48 ` Pavel Roskin [this message]
2008-07-22 21:37 ` Robert Millan
2008-07-22 22:01 ` Pavel Roskin
2008-07-22 22:09 ` Robert Millan
2008-07-22 22:41 ` Pavel Roskin
2008-07-24 17:02 ` Marco Gerards
2008-07-24 17:18 ` Pavel Roskin
2008-07-24 21:47 ` Christian Franke
-- strict thread matches above, loose matches on Subject: below --
2008-07-16 0:22 chaac
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=1216673313.11291.24.camel@dv \
--to=proski@gnu.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox