DJ Lucas wrote:
> On 08/23/2010 10:38 PM, Bruce Dubbs wrote:
>> Wow. I think that's a lot harder than just editing a file.
>
> Oh yes, it is certainly more difficult, but I was looking more at
> explaining how things are done (education has always been a top priority
> in the past). Also, by editing the grub.cfg file manually, we are
> making a recommendation that conflicts with one made by the developers.
Not really. That was put in at the request of the distros that don't
think their users are able to or want to edit a configuration file. The
warning 'DO NOT EDIT THIS FILE' is inserted by the grub-mkconfig script.
> Doing something like that has a tendency to bite you in the rear later
> on down the road. I do realize that I'm asking for a lot of changes to
> be made very late in the development cycle, but I really think it's
> wrong to recommend editing that file if the devs don't want you doing
> it. I'll be happy to do the leg work.
We can consider changes this significant for 6.8, but I think it's too
late for 6.7.
> We also used to have multiple examples in the book, for instance the
> prettier colors and the chainloading example. The chainloading example
> need not be Windows specific (though that is probably the most used).
> Chainloading is useful for booting to CD, floppy, (PXE?,) or any other
> bootloader, even another copy of grub, on a different partition.
GRUB2 configuration is already the longest part of any configuration
section in the book. There are so many options, that we can't cover
them all. I cover a very basic situation only. A hint would be
preferable for more complex options.
> Additionally, the possibility of destroying a good config if
> grub-mkconfig is run again kinda scares me.
If you are using GRUB Legacy, the filename is different. If you already
have GRUB2 installed, then running grub-mkconfig does the same thing
that's there unless some distro has made wild customizations. Also
grub-mkconfig only changes the working config if you use a separate
/boot partition.
> The following example would work just as well as manually editing the
> file, and would avoid the 'scare' I had mentioned above:
> cat >> /etc/grub.d/40_custom << "EOF"
> menuentry "LFS SVN 20100627, Linux 2.6.34" {
> linux /linux-2.6.34 root=/dev/sda13 ro
> }
> EOF
Yes, if there is:
1. A separate /boot partition used by kernels booting to multiple root
partitions, and
2. An already installed grub2.
> Finally, I'm still not very happy with that disaster created by the
> 10_linux script, which is why I suggested changing the permissions on it
> (and have done so locally).
My point exactly. Automation of grub.cfg is quite problematical.
I made the suggestion on the GRUB mailing list that the main grub.cfg
look for menu entries in other files in /boot/grub/ but they didn't respond.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
