On 01/29/2013 03:09 PM, Roman Bysh wrote:
On Tue 29 Jan 2013 02:20:32 PM EST, Andrey Borzenkov wrote:
В Tue, 29 Jan 2013 13:25:48 -0500 Patrick Shanahan
пишет: * Andrey Borzenkov
[01-29-13 13:03]: В Tue, 29 Jan 2013 12:50:33 -0500 Roman Bysh
пишет: First off, never edit the "grub.cfg" file manually due to the fact that when you run grub2-mkconfig command, all of the manual entries will disappear.
If you want to make chainloader entries, use the /etc/grub.d/40_custom file. Save your changes and then run:
grub2-mkconfig -o /boot/grub2/grub.cfg
On openSUSE you can also edit /boot/grub2/custom.cfg which is sourced during boot. No need to run grub2-mkconfig.
so cp /boot/grub2/grub.cfg /boot/grub2/custom.cfg and edit custom.cfg?
No copy, just edit.
if custom.cfg exists, is it used instead of grub.cfg or in addition to?
In addition to. custom.cfg is included into grub.cfg at runtime.
in editing "40_custom" it must be necessary to copy and alter "entire" sections of grub.cfg as "40_custom" appears to merely add lines to the "bottom" of grub.cfg. ie: its format/usage is not well explained, aics.
info grub2, Configuration - Simple Configuration. Did you read it?
I tried to add "video=1600x1200-32" to grub.cfg kernel parameters line via 40_custom and it only added a single line at the bottom of grub.cfg and had *no* effect.
There is "Additional kernel command line parameters" in YaST2 bootloader configuration (loosely translation back to English). Does it not work if you add it there?
thus far, usage/adaptation of grub2 as in unix text configuration files seem to be quite illogical and convoluted.
grub2.cfg is not unix text configuration file. It is script that is interpreted at runtime. grub-mkconfig is a convenience layer which automatically generates this script. Use of it is not mandatory and I have seen several projects that claim to do better job in maintaining grub.cfg.
I somehow after using grub2-mkconfig realized unwanted/unusable addiitons to the kernel parameters line in grub.cfg and could find *no* reference for correcting. On a "stab-in-the-dark" edited /etc/default/grub.old and was able to removed the unwanted chars from the grub.cfg kernel param lines. This is definitely *not* intuitive, expected, logical or documented (that I could find).
Let's be fair. Use of grub-mkconfig is documented well enough.
What exactly do you need to customize that is not documented?
I didn't know about "custom.cfg" even after dealing with the people at Bugzilla. They said that I had to use 40_custom for custom wording.
*And* editing existing entries. Any good examples of custom.cfg integration to grub.cfg? Roman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org