>> You may want to look here: >> https://help.ubuntu.com/community/Grub2 >> >> and probably here as well: >> http://www.gnu.org/software/grub/manual/grub.html >> <snip> >> > grub.cfg is the replacement for menu.lst >> >> Not exactly. The true replacement is /etc/default/grub > > I only have got one life and no time to read this. What are the reasons > not to edit grub.cfg?
You gave the reason yourself. grub.cfg is generated by a script, and therefore overwritten with updates. I also didn't like the Grub2 way of configuration first but that was because I was used to the Grub way already. Grub2 is much easier to automate updates, and it's more flexible. Still it's a bit unlogic (what have the boot loader scripts and config files to do in the main OS config directory, and why change partition numbering to start from 1 now but leave drive numbering starting from 0?) You can make static (not auto-updated) menu entries with the files in /etc/grub.d/ and set various menu behavior with /etc/default/grub, after that you call update-grub to write a new grub.cfg (misleading naming, should be "update-grubmenu" or similar) > I can post you my grub.cfg and you may tell me what files I have to > edit, in what way, to get exactly the grub.cfg I wish to have ;)? No way to RTM for you, sorry :-) But here is a pointer to what you probably need: https://help.ubuntu.com/community/Grub2#Custom%20Menu%20Entries > My grub.cfg does what I want So you want it to disappear on every update of kernel or Grub2? > I only can help editing grub.cfg! I don't know any argument not to edit > this file. Convenience is the argument for doing it like it's meant to be done by the makers. It's more complicated than it was with Grub but hey, once we were also unfamiliar with that one (and it was messy as it was). > A lot of people run echo by a script or use an editor, e.g. > echo "CONFIG_RT_GROUP_SCHED=n" >> .config > Do you always run an application and edit things with an app? Yes. Everything but copying keystrokes directly to a file at kernel level is running an application. echo, editors, command shells are all applications to the OS. The Grub2 config files, grub.cfg included, are still standard text files. Nothing will stop you from editing grub.cfg. It might even be necessary for example in a rescue situation. It's just not the most convenient way, because you will have to update it manually all the time (or perhaps make the scripts which overwrite it non-executable). > the DEs and basic stuff becomes more worse > than Windows. Don't worry. Where in Win have I ever been able to choose from several viable DEs and configure them to my liking. Now, I can make it more basic or more consumer-friendly as I like (or have no DE at all!). Have I ever met a Win bootloader which is automatically configured to let me choose which OS on the machine to load, regardless of manufacurer? But I'm not up-to-date, as I'm out of the scene since WinXP. Markus _______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
