| Autor |
Nachricht |
|
|
Titel: Dangerous command?
 Verfasst am: 23.07.2006, 03:54 Uhr
|
|
Anmeldung: 01. Feb 2006
Beiträge: 128
Wohnort: SF Bay area
|
|
A few weeks ago, I updated my kernel to 2.6.17-kanotix-1 from 2.6.16.16. That seemed to work ok, but right afterwords, I wanted to remove the old kernel and used "remove-kernel-completely". I did this from memory, but it tab-completed so I thought it was right. However, the command wanted to remove the newer kernel, so I aborted, but on reboot some modules failed to load and I got fatal errors. I saw the message that the kernel source tree was damaged. So I rebooted again this time into the old kernel. That worked ok, so I went to the irc to ask for help, and it was suggested that I just try to reinstall the new kernel. I did that and once again 2.6.17.1 worked. I left both kernels alone this time.
Then again this morning, thinking all was stable enough, I tried "remove-kernels-completely" and ran into the same problem. Again, I aborted when the command issued an ominous warning. Still, it borked my system even though I didn't follow through on the command. I got it back by booting into CLI init 3 and again reinstalling the 2.6.17 kernel. Having been burned twice, I started reading.  The remove kernels command should have been "remove-all-kernels-completely". I had left out the "all" previously.
Now I realize this was my fault, but I'm wondering what happened here. Obviously, doing "remove-kernels-completely" was very dangerous and is too close to "remove-all-kernels-completely". I don't want to do this to my system a third time, but if anyone knows whats going on here or would like to try it on a test installation, I'd be curious if you got the same result.
Sorry for the flurry of posts. They were all related to issues I had today, but I thought it was better to separate them.
Regards,
Ron |
_________________
To whom much is given, much shall be required.
|
| |
|
|
|
 |
|
|
|
Titel: RE: Dangerous command?
Verfasst am: 23.07.2006, 04:16 Uhr
|
|
Anmeldung: 13. Mai 2005
Beiträge: 732
Wohnort: Texas
|
|
| can't you remove them via synaptic? |
_________________
Always acknowledge a fault. This will throw those in authority off their guard and give you an opportunity to commit more.
Mark Twain
|
| |
|
|
|
|
|
|
|
Titel: RE: Dangerous command?
Verfasst am: 23.07.2006, 05:03 Uhr
|
|
Anmeldung: 12. Mar 2005
Beiträge: 1005
|
|
remove-all-kernels-completely removes all except the default kernel.
I didn't know about the 'remove-kernels-completely' command, that is obviously a dangerous command, like you said.
remove-all-kernels-completely is also not one of the better named commands by the way, since it doesn't actually remove all kernels completely, it just removes all non-default kernels completely.
I havent' tested it completely to see if it's actually the default kernel alone that it preserves, but I think that's what it is. |
|
|
| |
|
|
|
|
|
|
|
Titel: RE: Dangerous command?
Verfasst am: 23.07.2006, 05:32 Uhr
|
|
Anmeldung: 05. Dez 2005
Beiträge: 414
Wohnort: Auckland, New Zealand
|
|
If you want more control in what's getting removed, you can do this the following way:
... I upgraded my 2.6.17.3 kernel to 2.6.17.6-slh-up-1 (as the later kernel fixes a couple of security issues). So I can remove the 2.6.17.3 kernel like this:
First I do:
Code:
dpkg -l | grep '2.6.17.3'
(you can do dpkg -l | grep '2.6.16')
and look at the packeges installed, and then I can do:
Code:
apt-get remove --purge linux-doc-2.6.17.3-slh-up-1 linux-headers-2.6.17.3-slh-up-1 linux-image-2.6.17.3-slh-up-1
... this will remove everything for you including the grub entries.
Now I just reboot.
Pretty easy.
I personally wouldn't use synaptic. It might pay to do it in init 3 just in case. |
|
|
| |
|
|
|
|
|
|
|
Titel: RE: Dangerous command?
Verfasst am: 23.07.2006, 13:37 Uhr
|
|
Anmeldung: 17. Dez 2003
Beiträge: 16792
|
|
| Basically remove-all-kernels-completely is save, but not the remove-kernel-completely script, which I need to exchange the kernel on live cd. |
|
|
| |
|
|
|
|
|
|
|
Titel: Re: Dangerous command?
Verfasst am: 23.07.2006, 15:34 Uhr
|
|
Team Member
Anmeldung: 17. Dez 2003
Beiträge: 1109
Wohnort: Ganymede
|
|
|
feffer777 hat folgendes geschrieben::
A few weeks ago, I updated my kernel to 2.6.17-kanotix-1 from 2.6.16.16. That seemed to work ok, but right afterwords, I wanted to remove the old kernel and used "remove-kernel-completely".
There is absolutely nothing wrong with having multiple kernels installed simutaneously. In fact I never have less than 2 just in case there is a problem with one you can always boot back into the known working kernel and fix any issues you might have. The only situation (that I can think of) where you might want to keep only 1 kernel installed is lack of disk space. Just a suggestion.  |
_________________
Ubuntu - An ancient African word for "Can't install Debian"
|
| |
|
|
|
|
|
|
|
Titel: RE: Re: Dangerous command?
Verfasst am: 23.07.2006, 19:57 Uhr
|
|
Anmeldung: 01. Feb 2006
Beiträge: 128
Wohnort: SF Bay area
|
|
@mzilikazi: Thanks for the input, in the future, I probably will keep 2 kernels at least until, I'm pretty sure the newest is stable.
@Kano: I admit using "remove-kernel-completely" was my mistake. I should have followed my own notes. Just a suggestion: maybe one of these scripts could be renamed, to keep other users from getting into trouble.
Thanks for this great distro!
Ron |
_________________
To whom much is given, much shall be required.
|
| |
|
|
|
|
|
|
