All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: device.map (Re: Next release?)
Date: Tue, 22 Jul 2008 17:57:56 -0400	[thread overview]
Message-ID: <1216763876.5601.9.camel@dv> (raw)
In-Reply-To: <20080722213629.GB15111@thorin>

On Tue, 2008-07-22 at 23:36 +0200, Robert Millan wrote:
> On Mon, Jul 21, 2008 at 05:26:17PM -0400, Pavel Roskin wrote:
> > > 
> > > This is mostly implemented already.  I sent a proof of concept in a mail
> > > titled "[PATCH] disk/fs_uuid.c".
> > > 
> > > It will only search hard drives unless no match is found (in that case your
> > > boot is broken, so you wouldn't care much that floppy is being probed ;-)
> > 
> > Then all be need it to have an option in grub-install to enable this
> > logic.
> 
> Why an option?  Is there any situation in which it is known that boot will
> be unreliable (because embed disk != /boot/grub disk), and in spite of that
> you don't want UUIDs to be used?

I guess I was unclear.  It's not like I don't want the UUIDs to be used.
I don't want users to create a cross-drive setup unknowingly or without
knowing the consequences.  Failure of any of the drives will break the
loading.  There are many temporary portable drives and flash devices.
The intention of the user may be to make that drive bootable, not to
create a configuration that would require both the internal and the
external drives.

If the user is OK with the cross-drive install, using UUIDs should be
either the default or the only option.

-- 
Regards,
Pavel Roskin



  reply	other threads:[~2008-07-22 21:58 UTC|newest]

Thread overview: 37+ 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 [this message]
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
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

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=1216763876.5601.9.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 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.