[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Grub2 with multiple Debians

On 09/15/12 22:52, Hendrik Boom wrote:

On Sat, 15 Sep 2012 13:40:16 +0400, Dmitriy Matrosov wrote:


On 09/15/12 00:42, Hendrik Boom wrote:

On Fri, 14 Sep 2012 23:25:03 +0300, Andrei POPESCU wrote:


On Vi, 14 sep 12, 17:12:38, Hendrik Boom wrote:


Of course, after I've made my copy (with slight changes to
/etc/fstab) I have two nearly identical sets of partitions, so it may
be tricky to tell them apart.  Is grub2 clever enough to figure it
all out anyway? And what data does it use to this end? (so I can make
sure it's right!)


UUIDs? What failure mode(s) do you have in mind, because I can't think
of any.


It probably is os-prober that I mean.  The misconfiguration I have in
mind is matching one system's /boot with another systems's /.  I've had
it happen on a laptop sometime ago. and it sure messed up my upgrades.
I have no idea how it happened, but it has made me paranoid.

-- hendrik




Hi.

Useless entries in grub.cfg (with non-matched kernel and root, e.g.
kernel from stable and root from testing) or probably even no correct
one - is normal for 30_os-prober and 10_linux scripts. I don't think,
that there is a simply way to fix them.


You'd think that os-prober could use the entries in /etc/fstab to
identify the /boot that goes with a particular root partition.


May be this will work. May be not. But there will be many problems with
this, and rewriting os-prober (instead just some or several configs) is not
the last of them (i mean, you will have problems during grub update if your
patches have not yet accepted upstream). And if you want my opinion, i don't
think this will work. First, there is no guarantee, that corresponding /boot
will be mentioned in fstab. Second, /boot may be common for all distributions, 
and the problem will be to identify correct kernel. And, third, you should
not just figure out correct kernel for current OS, but for all others as well.
Reply to: