This is sort of deliberate - configuration files generally belong in
/etc and it's easier to apply appropriate rules (e.g. for package vs.
local edits) there. /boot/grub/grub.cfg is an exception because the
boot loader has to read it out of a filesystem it can read, and it can't
always read from /etc directly. That was a more important purpose for
/boot than being shared between multiple OSes.
I would be very worried about encouraging multiple OSes to use the
configuration files in /etc, because their format is not stable, and
it's quite possible for them to change substantially between different
versions of GRUB. For that matter, I would expect each OS to want to
own its own versions of those configuration files, which would often be
different.
In cases such as this which are evidently quite specialised, would it be
worth simply writing your own /boot/grub/grub.cfg from scratch, and
disabling the configuration file generation facilities (e.g. by using
dpkg-divert on /usr/sbin/update-grub and installing a replacement script
which does nothing)?
** Changed in: grub2 (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: grub2 (Ubuntu)
Status: New => Triaged
--
grub2 layout no longer suitable for shared boot/multi-distro
https://bugs.launchpad.net/bugs/669413
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
