On Thu, 21 May 2015 07:34:58 -0400, Rich Freeman wrote:

> > Also, you need to copy 40_custom and then add your lines to that.
> > This is because files in /etc/grub.d are executed, so it needs to be
> > a shell script.

> If you're just going to hand-edit your config file, I don't see much
> point in sticking this stuff in /etc/grub.d.  Just hand-edit your
> config file and forget about grub2-mkconfig.

You sill need to edit something each time you update your kernel, unless
you can use symlinks, and running grub2-mkconfig may give you useful
fallback entries from 10_linux.

> 40_custom is more about adding one more entry to an auto-generated
> menu, such as having an entry for booting another OS, or a rescue CD
> image, or whatever.

40_custom is also just and example. You can have any script you want in
there. I wrote a script that auto-generates the entries *I* want and
removed the executable bit from 10_linux. Now I get multiple entries for
all my installed kernels with the correct boot options.


-- 
Neil Bothwick

Despite the cost of living, have you noticed how it remains so popular?

Attachment: pgphLiDvfhuGv.pgp
Description: OpenPGP digital signature

Reply via email to