This mandatory behavior of update-grub to convert kopt entries to UUIDs
really needs to be reconsidered.  I understand why from a user-
friendliness or newbie point of view one might want this behavior, but
there needs to be an option somewhere (even if it's somewhere esoteric)
which allows a user to turn this behavior off.

I've been using Linux nearly exclusively since 1996, starting with
Debian 1.2 (rex) and switching to Ubuntu more recently.  Despite the
struggle that I've sometimes had with Linux's lack of user-friendliness,
the argument I've always been able to make is that it "does what I tell
it to do, not what somebody in Redmond or Cupertino thinks it should
do."  The reason many people choose Linux is for flexibility and control
over their computers.

I've had many experiences over the past 11 years when a 
developer/package-maintainer/distribution chooses a *default* behavior that 
I've disagreed with, but
this is one of the very few times when I've been *forced* to patch (re-patching 
anytime an upgrade occurs) my system, switch distributions, or fall in line 
with somebody else's idea of how I should use my computer.

Please give me the option of choosing whether update-grub should 'fix'
my kopt line or leave it be.

-- 
edgy update-grub destroys kopt
https://bugs.launchpad.net/bugs/62195
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to