[Bug 538884] [NEW] No appropriate method for modifying specfic menuentry

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Sebastien Bacher (seb128):

Binary package hint: grub2

With grub2 (grub-pc 1.97~beta4-1ubuntu4.1) on Ubuntu 9.10, there is no
appropriate mechanism for adding command-line parameters to a specific
menuentry.

For example, I need to add "disable_esco=true" (bluetooth subsystem
kernel parameter) to the "Ubuntu, Linux 2.6.31-20-generic" menuentry. I
*do not* want this parameter for any other menuentry. Similarly, I only
want 1 (recovery mode) menuentry.

I understand that I could create a custom script, say
/etc/grub.d/07-custom, that would have a menuentry in it copied from
/boot/grub/grub.cfg. Unfortunately, this approach has several drawbacks
that make it unsuitable. First, it forces this menuentry to be before
any kernel enumerated by the 10-linux script, even if it's a prior
version to other kernels. Second, the script has no access to the
functions available in 10-linux (like the UUID get).

I'm also aware that I could edit /boot/grub/grub.cfg directly.
Unfortunately, this is worse because *there is no way* to protect the
contents of grub.cfg. The kernel upgrade packages overwrite this file
regardless of the file attributes (like, what if I forget that I've made
custom changes to this file when I upgrade the kernel in 6 months).

Adding a kernel parameter should not be this difficult.

** Affects: grub2 (Ubuntu)
     Importance: Wishlist
         Status: Triaged


** Tags: patch
-- 
No appropriate method for modifying specfic menuentry
https://bugs.launchpad.net/bugs/538884
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is a direct subscriber.