From: adrian15 <adrian15sgd@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: multidistro grub2 idea
Date: Sat, 11 Aug 2007 21:34:22 +0200 [thread overview]
Message-ID: <46BE0F3E.9060606@gmail.com> (raw)
In-Reply-To: <78323d480708060805x89a7732j21eb9a7c990cfa88@mail.gmail.com>
Mani A escribió:
>> #1) All Linux installers should set or reuse a ext2 partition next to
>> the windows one as a /boot one where grub2 is installed.
> .. . if the dreaded OS exists. But a single /boot partition is not
> preferable over 'but from anywhere' principle.
Well.. this is the old discussion: Centrality versus Redundancy and its
problems.
>
>> #2) /boot/grub/
>>
>> will have a new folder called:
>>
>> /boot/grub/menu/
>>
>> which will be filled with .cfg files from the different distros that
>> are installed in a computer.
>
> It will be a good thing if, if grub2 is installed to the mbr of the
> active partition and if a new OS is going to be installed, then we
> must be able to tell grub2 about it and accordingly it must be able to
> update the .cfg, when the new OS tries to write to the MBR of any of
> the partitions.
How would you detects this partition boot records changes? Saving a
backup somewhere in the linux system and running an utility on the boot
that compares backup to real partition boot sectors and asks you if you
want to update cfg?
That's your idea?
adrian15
next prev parent reply other threads:[~2007-08-10 16:39 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
2007-08-06 15:05 ` Mani A
2007-08-11 19:34 ` adrian15 [this message]
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=46BE0F3E.9060606@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.