On Sat, 11 May 2013 12:39:41 +0100, Stroller wrote:

> >> So, how was  the switch? Uneventful? The more I read, and once I
> >> learned you could still use a monolithic config file, the less this
> >> looks like a big deal...  
> > 
> > STILL use a monolithic config file? GRUB2 has to use a monolithic
> > config file, usually /boot/grub2/grub.cfg. grub-mkconfig is not a
> > bootloader, just an easy way of managing that monolithic
> > configuration file.  
> 
> You seem to have take it as a criticism, but I read previous message as
> approving of monolithic config files.
> 
> "grub2 looks ok, because it still uses a monolithic config file"

I read it different because of the use of the word "could". It is not an
option with GRUB2, it is a requirement. The format and name of the file
have changed, but it is still a single file. The only optional aspect is
how you create that file. With the old GRUB you have to write it by hand,
now you have a second option.

There seems a perception that you have to use the files in /etc/grub.d
and /etc/default, but this a absolutely not the case, and never has been. 


-- 
Neil Bothwick

If you got the words it does not mean you got the knowledge.