Grub2 grumbles

[D. Hugh Redelmeier]

| From: Timothy Hildred <timhildred-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org>

| So instead of editing the grub.cfg you edit /etc/boot.d/40_custom to include
| an entry like the one described above:
|
| menuentry "Microsoft Windows XP Professional (on /dev/sda1)" {
|        insmod part_msdos
|        insmod ntfs
|        set root='(hd0,msdos1)'
|        search --no-floppy --fs-uuid --set aa1ccf831ccf48d1
|        drivemap -s (hd0) ${root}
|        chainloader +1
| }
| 
| and then run your update-grub.

Yes, but...

I wrote in my original message:

	There is no clean and simple way for me to take control (I
	don't count writing those arcane scripts as a solution)

As far as I know, the only clean way of configuring is to add scripts
to /etc/boot.d/ (as you suggest).  If I modify scripts there, I'm
fiddling with files owned by something (probably the grub package).
Such changes are likely to be compromised in some way by updating the
grub package.

This directory is analogous to the System V startup scripts in
/etc/init.d (also on many Linux distros).  On Red Hat systems there
are tools designed to manipulate that directory (netsysv, chkconfig).
I know of no such tools for /etc/boot.d .

Many of the problems I mentioned are not missing entries but entries
that are not done the way I want.  That is awkward to fix.

I don't even know if scripts added to the directory will survive grub
package updates.  One would hope so.
--
The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists