Quote:
Originally Posted by merchtemeagle
See chapters:
6. Adding Entries to Grub 2
7. Removing Entries from Grub 2
|
Erm.. Chapters 6 and 7 of which?
Actually - I feel very much as marozsas does. I can fully understand that grub2 was thought up with the intentions of offering advantages, but it fails in some of its mission if it causes me to waste very long times in trying to discover its new ways, without borking working systems several times. I want and need to multi-boot. I should not have to be a Linux scripting expert to do it!
The fashion for burying desired user choices in complexity, to almost force users to give up and simply accept the one-click no-function default is beginning to get tiring.
grub.conf was simple, but could be made powerfully versatile if the user read the manual and invoked the commands.
menu.lst, so far as I can tell was only another name for grub.conf, with no other redeeming features (if I be unfair here - do tell)! Thus we have added
symlinks left laying about in /boot/grub, so that
menu.lst points to a
grub.conf, and sometimes vice-versa.
Then - we were assailed by the Debian update work-around (in case the kernel changed), using special groupings of the comment signal symbol #, such as ### to do their thing without upsetting grub, which would simply see the lines as a comments.
Now we have a new game. Find your way to /etc/grub.d. The README is quite opaque to a user like me..
Code:
All executable files in this directory are processed in shell expansion order.
00_*: Reserved for 00_header.
10_*: Native boot entries.
20_*: Third party apps (e.g. memtest86+).
The number namespace in-between is configurable by system installer and/or
administrator. For example, you can add an entry to boot another OS as
01_otheros, 11_otheros, etc, depending on the position you want it to occupy in
the menu; and then adjust the default setting via /etc/default/grub.
The other files there are complex scripts, except for one. 40_custom is supposedly where a user adds menu entries. Nowhere can one see the boot order in a simple document, including how to set timeouts and saveboot options. I am unsure it is a Ubuntu thing, or a
grub2 thing, or a bit of both.
This arrangement may be the dog's dangly bits (British colloquialism-forgive!) to the proud inventors, but I say, they just made us user's life harder. Truly, this is not just about unfamiliarity, or a reluctance to RTFM. The actual functionality has been reduced so far as users are concerned, even if it has been expanded (they say) for the experts.
I suppose I had better get to a question. So where is a kindly explanation, with maybe some examples, on what to do to multiboot?