Re: Don't edit /etc/grub.d/grub.cfg

2010-08-24 Thread Bruce Dubbs
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

Re: Don't edit /etc/grub.d/grub.cfg

2010-08-24 Thread Andrew Benton
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 inste

Re: Don't edit /etc/grub.d/grub.cfg

2010-08-23 Thread DJ Lucas
On 08/23/2010 10:38 PM, Bruce Dubbs wrote: > DJ Lucas wrote: >> Additionally, we can comment out the search line in 00_header (since it >> is pretty much useless on default build) and add some additions there >> (like background image, or prettier colors, etc.). I think I spoke too soon on that

Re: Don't edit /etc/grub.d/grub.cfg

2010-08-23 Thread Bruce Dubbs
DJ Lucas wrote: > 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? Because it requir

Don't edit /etc/grub.d/grub.cfg

2010-08-23 Thread DJ Lucas
-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 inten