Grub Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Colin D Bennett <colin@gibibit.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: proski@gnu.org
Subject: Re: Next release?
Date: Wed, 16 Jul 2008 07:11:26 -0700	[thread overview]
Message-ID: <20080716071126.170a1d58@gibibit.com> (raw)
In-Reply-To: <1216165935.9604.26.camel@dv>

On Tue, 15 Jul 2008 19:52:15 -0400
Pavel Roskin <proski@gnu.org> wrote:

> On Wed, 2008-07-16 at 01:32 +0200, Yoshinori K. Okuji wrote:
> 
> > If a boot drive is the same as a root drive, you are right.
> > Otherwise we need to do so.
> >
> > I think we have seen tons of examples with GRUB Legacy which may
> > not be solved automatically in all cases. If one digs into the
> > archive of bug-grub, I guess several cases would be found easily.
> > With GRUB 2, we can avoid embedding BIOS drive numbers in many
> > cases, using UUIDs or labels or files. But this does not always
> > work, so I am afraid that we need to support device.map, even if it
> > is an evil necessity.
> 
> That's a very advanced setup.  I actually cannot imagine why anyone
> would use different boot and root drives.  Well, maybe the boot drive
> has no partitions that GRUB or the host OS can access? 

I have used machines that have multiple Linux versions spread across
two drives, but one common /boot partition so they can all be booted
from GRUB.  This doesn't seem unusual to me.



  reply	other threads:[~2008-07-16 14:11 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 [this message]
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
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=20080716071126.170a1d58@gibibit.com \
    --to=colin@gibibit.com \
    --cc=grub-devel@gnu.org \
    --cc=proski@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