On Tue, Jun 29, 2010 at 11:34 AM, Ramnarayan.K <[email protected]> wrote: > 2010/6/29 Abhishek Amberkar [अभिषेक] <[email protected]>: >> >> Why did this work? cause dpkg doesn't take care of dependencies? > > well maybe it worked but partially > > my boot still was at 100 % usage and on rebooting this status did not change
Because you removed wrong package. You were supposed to remove linux-image-<something>. The package you removed didn't have any files in /boot. > > so went to synaptic and tried to get rid of yet another older kernel > > the process got stopped with the first error message - not enough space > > so this time i went into /boot via sudo nautilus and deleted files > that had to do with 2 of the older uninstalled kernels You shouldn't really do that. You should remove kernels in proper way. > > dpkg did uninstall but not physically remove it. So no new space was created. Wrong conclusion. Please see above. > So understanding this i dpkg -r one more linux kernel and have > physically removed some more stuff from /boot now reading only 78 $% > usage > > so am trying now through synaptic to remove some of the other older kernels > > it seems i have from 2.6.31-16 through to .22 installed - thats quite a bit Good that synaptic is working for you now. It would have also worked if you would have removed correct package with dpkg. :-) Onkar -- Passion - Some people climb mountains - others write Free software. Don't ask why - the reason is the same. -- ubuntu-in mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-in
