4 ms·
>you should be able to edit grub.cfg You mean the grub configuration file that shouldn't be edited? # # DO NOT EDIT THIS FILE # # It is automatically gener
by jaclaz 4y ago
>you should be able to edit grub.cfg
You mean the grub configuration file that shouldn't be edited?
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
It is a pet peeve of mine, but according to the good people that wrote GRUB2, grub.cfg is subject to auto-magic modifications when updating the (main) Linux install, so it shouldn't be edited manually but rather sort of scripted.
For a GRUB2 installed to harddisk, modifications should be written to
40_Custom
https://help.ubuntu.com/community/Grub2/CustomMenus https://help.ubuntu.com/community/Grub2/CustomMenus
otherwise (it depends on which Linux distro is the "main" one) it can happen that at next update the grub.cfg is recreated losing your changes to it.
- yellowapple 4y agoRight, that's totally what I meant; I totally don't just ignore that warning and reapply my patch if I ever accidentally run grub-mkconfig after initial install ;) In any case, something to the effect of root (hd0,1) kernel /tinycore/vmlinuz tce=sda1/tinycore/tce vga=794 initrd /tinycore/core.gz in GRUB's shell should do the trick no matter what might lurk in grub.cfg.
- jaclaz 4y agoYep. :) And (as a side note) one could make a separate, static .cfg, let's say tiny.cfg and load it from shell with configfile, aka configfile /tiny.cfg.