On Mon, 26 Sep 2005 11:31:16 -0400, Joe Mason <[EMAIL PROTECTED]> said:
> On Sun, Sep 25, 2005 at 11:03:14PM -0700, Debian Bug Tracking System wrote:
>> Hi,
>>
>> Why is this message not enough?
>>
>> manoj
>>
>> You are running a kernel (version $running) and attempting to
>> remove the same version. This is a potentially disastrous
>> action. Not only will /boot/vmlinuz-$running be removed, making it
>> impossible to boot it, (you will have to take action to change your
>> boot loader to boot a new kernel), it will also remove all modules
>> under the directory /lib/modules/$running. Just having a copy of
>> the kernel image is not enough, you will have to replace the
>> modules too.
>>
>> I repeat, this is very dangerous. If at all in doubt, answer no. If
>> you know exactly what you are doing, and are prepared to hose your
>> system, then answer Yes.
> That message would be fine, but I've never seen it before.
> (Specifically, not when following the steps given in the original
> bug submission.) Unless it was added in a later version of the
> tools than I have installed, it seems to be broken.
No, it has been here all along. You just aborted too
early. The issue is whether a user could have a running kernel yanked
out from under them with no warnings -- and, really, they are
not. You haven't shown that a running kernel was removed either: you
just showed that apt does not warn, and that is perfectly all
right -- apt should not have to know about such things.
manoj
--
Landru! Guide us! A Beta 3-oid, "The Return of the Archons", stardate
3157.4
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.debian.org/%7Esrivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
