Adding kernel parameters to _other_ OS in grub

[NoOp]

On 05/25/2010 07:21 PM, Tom H wrote:
> On Tue, May 25, 2010 at 9:55 PM, NoOp <> wrote:
...
>> I know that grub.cfg states:
>> # DO NOT EDIT THIS FILE
>>
>> 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.
>>
>> 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.
> 
> Editing 40_... would only be required if the kernel on the install(s)
> being referenced by 40_... is(are) updated so it would entail less
> editing that grub.cfg.
> 
> *If* the grub developers ever implement such a system, I would hope
> that they would use GRUB_CMDLINE_LINUX_DEFAULT_hdxy and
> GRUB_CMDLINE_LINUX_hdxy to apply different kernel parameters to any
> install on a box.
> 

Ah. Now that's a good point!

Found a good writeup regarding grub2 here:
http://kubuntuforums.net/forums/index.php?topic=3106368.0
SECTION 4 has some interesting bits regarding symlinks that I'd not seen
anywhere else:
4 ways to boot an OS: configfile,  symlinks,  direct booting,  chainloader