:~# apt-get upgrade Reading Package Lists... Done Building Dependency Tree... Done The following packages have been kept back abiword abiword-common abiword-plugins ark debhelper gdm gettext-el gnome-applets gnome-control-center gnome-core gnome-panel gnome-panel-data gnome-session gnome-terminal gnome-utils karm kate kcalc kcharselect kcoloredit kcron kdebase kdebase-libs kdepasswd kdepim-libs kdf kdict kdm kedit kfind kghostview khexedit kiconedit kit kjots kmail knewsticker knode knotes konqueror konsole korganizer korn kpackage kpaint kruler kscreensaver ksirc ksnapshot ksysv ktimer kuser kview libgal-data libvorbis0 nethack-x11 rep-gtk rep-gtk-gnome sawfish-gnome secpolicy 0 packages upgraded, 0 newly installed, 0 to remove and 60 not upgraded. 2 packages not fully installed or removed. Need to get 0B of archives. After unpacking 0B will be used. Do you want to continue? [Y/n] y Setting up exim (3.35-1woody1) ... hostname: Host name lookup failure hostname --fqdn gave non-zero exit code 256 dpkg: error processing exim (--configure): subprocess post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of mutt: mutt depends on exim | mail-transport-agent; however: Package exim is not configured yet. Package mail-transport-agent is not installed. Package exim which provides mail-transport-agent is not configured yet. dpkg: error processing mutt (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: exim mutt E: Sub-process /usr/bin/dpkg returned an error code (1) ----------------------- A new kernel image has been installed. at /boot/vmlinuz-2.4.18-bf2.4 (Size: 1235kB) Symbolic links, unless otherwise specified, can be found in / LILO sets up your system to boot Linux directly from your hard disk, without the need for booting from a boot floppy. WARNING If you are keeping another operating system or another version of Linux on a separate disk partition, you should not have LILO install a boot block now. Wait until you read the LILO documentation. That is because installing a boot block now might make the other system un-bootable. If you only want to run this version of Linux, go ahead and install the boot block here. If it does not work, you can still boot this system from a boot floppy. Would you like to create a boot floppy now? [No] You already have a LILO configuration in /etc/lilo.conf Install a boot block using the existing /etc/lilo.conf? [Yes] Testing lilo.conf ... An error occurred while running lilo in test mode, a log is available in /var/log/lilo_log.2025. Please edit /etc/lilo.conf manually and re-run lilo, or make other arrangements to boot your machine.