Adding kernel parameters to _other_ OS in grub

[Dotan Cohen]

On 26 May 2010 04:55, NoOp <glgxg at sbcglobal.net> wrote:
> I know that grub.cfg states:
> # DO NOT EDIT THIS FILE
> #
> # It is automatically generated by /usr/sbin/grub-mkconfig using templates
> # from /etc/grub.d and settings from /etc/default/grub
>
> I wonder if in this case it might be easier to just add them to the end
> of the linux line(s) in /boot/grub/grub.cfg. Of course you'd need to
> check/duplicate on new kernel updates. But you'd need to do similar with
> 40_custom as well.
>

Isn't that exactly what 40_custom is for? What is the advantage of
adding the entries directly to grub.cfg?


> *Normal disclaimers for backing up et al apply*
>
> A better solution would be to have the ability for /etc/default/grub
> 'GRUB_CMDLINE_LINUX' to recognise where to apply the parmeter. For example:
>
> GRUB_CMDLINE_LINUX=2,"quiet splash"
>
> where the '2' would reference the 2nd menuentry.
>

It would be great if that existed! I will probably file a feature
request at Grub for that, surely I am not the only fool in the world
who dual boots!


> You could then run:
>
> $ grub-mkconfig -o test.cfg
>
> to output a test.cfg file to see if the action is applied properly. Or
> simply:
>
> $ $ grub-mkconfig
>
> to view what the result would be on the terminal screen.
>

Thanks, I will do the test run before commiting, naturally.


-- 
Dotan Cohen

http://gibberish.co.il
http://what-is-what.com