[bug #36132] Requires write access outside of /boot

[Tamus Royce]

Follow-up Comment #2, bug #36132 (project grub):

Another issue I am having:

When using multiple linux distributions on the same hard drive, it is
difficult to syncrhonize /etc/grub2 between different root / partitions.

Grub's scope is dependent on a single boot partiton.  So all configuration
information should be shared inside of that single boot partition.

1.  Have partition 1 as the boot partition.
    a.  linux (hd0,gpt1)/kernel-gentoo root=/dev/sda2    #server
    b.  linux (hd0,gpt1)/kernel-sabayon root=/dev/sda3   #desktop
    c.  linux (hd0,gpt1)/kernel-tiny-core root=/dev/sda4 #family

2.  Have partition 2 as Gentoo root partition.
3.  Have partition 3 as Sabayon root partition.
4.  Have partition 4 as TinyCore root partition.
5.  Have partition 5 as swap space.

Modifying customization on Gentoo and applying it wipes out Sabayons
customization.

I guess this is a future feature, because work-arounds are possible in this
scenario.

The except to this is TinyCore, which has Read-Only issues and stores
configuration directories in a non-standard location.  It may be a
distributition specific issue.

Unless other live-dvd Linux distros suffer from this issue (which are used to
modify systems, but not allow modifications to themselves...e.g. Linux
LiveCD/DVD recovery disks).

I also like the idea of the configuration persisting after the loss of the
root partition which it was installed to.

NOTE:  I would not work on this until after other more important issues are
resolved!

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?36132>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/