I demand that Ant may or may not have written...

> I think I broke something on my Debian while installing a Kernel image
> (amd64) and ran out of disk space (it didn't tell me that and I was AFK
> during the installation to ctrl-c/abort). Here's the log [...]:

> # apt-get install linux-image-2.6.18-4-amd64
> Reading package lists... Done
> Building dependency tree... Done
> The following NEW packages will be installed:
>   linux-image-2.6.18-4-amd64
> 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> Need to get 16.8MB of archives.
[snip]
> Testing for an existing GRUB menu.lst file ... found:
> /boot/grub/menu.lst
> Searching for splash image ... none found, skipping ...
> Found kernel: /boot/vmlinuz-2.6.18-4-amd64
> Found kernel: /boot/vmlinuz-2.6.18-4-k7
> Found kernel: /boot/vmlinuz-2.6.18-3-k7
> Updating /boot/grub/menu.lst ... done
>
>
> # df
> Filesystem           1K-blocks      Used Available Use% Mounted on
> /dev/hda1               270969    268661         0 100% /
[snip; no /boot]
> # apt-get clean
> # df
> Filesystem           1K-blocks      Used Available Use% Mounted on
> /dev/hda1               270969    268661         0 100% /
[snip; a small usage reduction in /var]
> # apt-get remove linux-image-2.6.18-4-amd64
> Reading package lists... Done
> Building dependency tree... Done
> The following packages will be REMOVED:
>   linux-image-2.6.18-4-amd64
> 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
> Need to get 0B of archives.
> After unpacking 65.3MB disk space will be freed.

Big hint there - maybe you want to remove a kernel image which you know that
you won't be using again first. (Obviously not the one currently in use!)

[snip]
> The link /vmlinuz is a damaged link
> Removing symbolic link vmlinuz
> Unless you used the optional flag in lilo,
>  you may need to re-run your boot loader[lilo]

Hmm, problem...

[snip]
> # df
> Filesystem           1K-blocks      Used Available Use% Mounted on
> /dev/hda1               270969    204863     51650  80% /

Well, there you go. 15MB short.

[snip]
> Do I need to worry about those errors? If so, then what do I need to fix
> this? I am afraid to reboot my computer and find Debian not able to boot
> up. 

Probably the best thing to do is to start building your own stripped-down
kernels. Or shrink another partition by 64MB or so and create a /boot
partition from it - mount it elsewhere, move files to it from your existing
/boot, add a suitable fstab entry, unmount it and remount it over your old
/boot, re-run lilo.

--
| Darren Salt    | linux or ds at              | nr. Ashington, | Toon
| RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army
| + Generate power using sun, wind, water, nuclear.      FORGET COAL AND OIL
.

Descartes of Borg: "I assimilate, therefore I am."

[ Post a follow-up to this message ]