http://brainstorm.ubuntu.com/item/22408/
I'm proposing this idea because it's incredibly easy to accidentally render a system unbootable, and it's disproportionately difficult to fix it once it's in that state. I don't really think this is a *bug* per se, since the package manager was obeying the user input.

[34 votes] Solution #1: Restrict uninstall of last kernel image


[9 votes] Solution #2: Remove old kernel image once the new one is verified


]]> en-us Thu, 12 Nov 2009 00:50:59 +0000 Thu, 19 Nov 2009 14:51:21 +0000 QAPoll module http://brainstorm.ubuntu.com/idea/22408/ Thu, 12 Nov 2009 05:59:21 +0000
If we are going to restrict this, we may as well restrict users from manually running "sudo rm -rf /boot/*" which I find to be a bad solution.

Instead we should be INFORMING users that certain actions are not safe to run. For packages that need to be there (kernel, etc), as note or warning next to the package such as "warning, this package is required for the proper running of your computer" should be enough. If users are going to read that, then there's not much else you can do.]]> Thu, 12 Nov 2009 06:33:15 +0000
"sudo" powers require great responsibility. And typing the password should be enough a warning.]]> Thu, 12 Nov 2009 08:44:34 +0000 If kernels won't be taking space on root partition, then users wouldn't try to do it manually with sometimes bad outcome.]]> Thu, 12 Nov 2009 13:08:07 +0000 Thu, 12 Nov 2009 22:46:00 +0000
That could be a problem, considering how often sudo is required to do tasks. Ubuntu users get as used to sudo and giving permissions as users of newer Microsoft operating systems have gotten used to clicking through UAC boxes.

There is a good point here in having a "second layer" that is more serious than the first.]]> Sat, 14 Nov 2009 15:17:13 +0000
Common (daily) work should be possible without any root permissions and the term of 'administrating' a computer by typing the 'administrator password' needs to be emphasized in turn.]]> Thu, 19 Nov 2009 14:51:20 +0000