Re: non-debian kernels -- bizzar?
Hi,
>>"joost" == joost witteveen <joost@rulcmc.leidenuniv.nl> writes:
joost> Does anyone else think it should be possible to remove the
joost> current running kernel, if you answer "yes" to an explicit
joost> question that informs you about the possible dangers? Or, do I
joost> simply have to reboot into kernel 2.0.29 (also still on my HD),
joost> then remove the debian kernel package-2.0.30, and reboot into
joost> my own 2.0.30 again? Really, I don't see why I should have to
joost> go through all this trouble, or what benefit there is in making
joost> users go through all this. (Yes, I know I can also change the
joost> "exit 1" to an "exit 0" in the prerm, but the example above is
joost> just to show how easy it is go get around the test without
joost> really knowing what you do).
This is not bypassing the test, this is telling the system
that yes, I have another kernel, so please go ahead and remove
2.0.30. (this is precisely what the prerm wanted to know.
The benefit is that even a Debian developer find it very hard
to get rid of a kernel that is the same version as the one running
;-). This will make it very hard for a novice to totally hose the
system
If it is this easy for you to bypass the problem, it means
that someone who knows what they are doing can get rid of the
package.
I do not see a problem.
manoj
--
"The weed of crime bears bitter fruit." The Shadow
Manoj Srivastava <url:mailto:srivasta@acm.org>
Mobile, Alabama USA <url:http://www.datasync.com/%7Esrivasta/>
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: