On 24/08/10 04:01, DJ Lucas wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Wow, first time I've messed with grub 2, and I had like 6 kernels still > hanging around and the result was just plain ugly! Is there any reason > we are recommending that the user edit grub.cfg manually instead of > using the /etc/grub.d directory as intended? > > The grub config files are simply shell scripts, and stdout gets put into > the output file of grub-mkconfig (you can redirect to stderr in order to > print a nice message to the screen as in the example below). I'd much > rather get rid of /etc/grub.d/10_linux (by making it not executable) and > let the users define what is needed as opposed to searching for kernels > to make the file.
Personally I configure grub with --sysconfdir=/tmp so /etc/grub.d is not created. Editing grub.cfg is much simpler than trying to work with the scripts in /etc/grub.d IMO ;) Andy -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
