All of lore.kernel.org
 help / color / mirror / Atom feed
From: adrian15 <adrian15sgd@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: multidistro grub2 idea
Date: Fri, 03 Aug 2007 19:55:26 +0200	[thread overview]
Message-ID: <46B36C0E.2070901@gmail.com> (raw)
In-Reply-To: <d019d53c0707220721r123648efyd751a2602c71adb7@mail.gmail.com>

BVK escribió:
> On 7/23/07, adrian15 <adrian15sgd@gmail.com> wrote:
> 
>> I think that if grub2 is going to have scripting and so many new
>> features we should take advantage of them and change the way computers
>> do boot.
>>
>> #1) All Linux installers should set or reuse a ext2 partition next to
>> the windows one as a /boot one where grub2 is installed.
>>
>>
>> What are your thoughts about this idea?
>>
> 
> Can't grub2 merge menu.lst files from all grub2-readable partitions
> and generate a menu dynamically? I dont know, but does this require
> grub2 to load *all* filesystem modules on boot-up?
> 

That's quite similar to how Super Grub Disk works when you try to boot
an existing linux and it seeks for all the menu.lst.

I am talking about changing the boot world. Having an unique boot
partition might make things much simpler.

Although I also think that if you loose this partition you are in
trouble so there should be a backup of this partiton somewhere on the
root partitions. :)

adrian15




  reply	other threads:[~2007-08-03 17:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-23 13:42 multidistro grub2 idea adrian15
2007-07-22 14:21 ` BVK
2007-08-03 17:55   ` adrian15 [this message]
2007-08-06 15:05 ` Mani A
2007-08-11 19:34   ` adrian15
2007-08-10 22:59     ` Mani A

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=46B36C0E.2070901@gmail.com \
    --to=adrian15sgd@gmail.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.