Follow-up Comment #4, bug #36132 (project grub):
I do understand. You might not be seeing the tight-coupling that is
happening.
Grub-Legacy had files stored in this manner (the internal code may have been
tightly-coupled, but the program functionality was not).
1. grub-mkconfig (userspace program)
2. configuration files (boot partition)
3. grub runtime (mbr table)
What is happening now is the configuration files are being tightly coupled
with grub-mkconfig (from a usability perspective, not coding), by being on the
same partition as grub-mkconfig.
Applying grub configuration effects all partitions. Why would the
configuration be located outside of the boot partition?
--------------------------------------------------------------
If a root partition was being booted from (/boot directory located in /), the
same per-root-partition configuration would be available.
--------------------------------------------------------------
I don't like to ask questions within issues...But can you re-generate the
configuration files (including customization) from grub runtime if the
configuration files are lost?
This is a feature request (which understandably, not all features make it into
applications).
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?36132>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-grub mailing list
Bug-grub@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-grub
