Package: lilo Version: 1:22.8-6.3 Severity: normal I have a rather old router that is only using a kernel-image, which is smaller then 1.2MB and has no initramfs/initrd. Since this hardware is rather old I did not enable large_memory after the upgrade to the latest version. The problem is that there is a check in postinst which looks for the option and if not set then checks for a kernel-image AND an initrd-image. Since there is no initrd image, this fails and postinst display an error, which is wrong.
I did put this on normal since in this case lilo is not called. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i586) Kernel: Linux 2.6.27 Locale: LANG=C, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages lilo depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii libc6 2.7-15 GNU C Library: Shared libraries ii libdevmapper1.02.1 2:1.02.27-4 The Linux Kernel Device Mapper use ii mbr 1.1.10-1 Master Boot Record for IBM-PC comp lilo recommends no packages. Versions of packages lilo suggests: pn lilo-doc <none> (no description available) -- debconf information: liloconfig/fstab_broken: liloconfig/banner: liloconfig/use_lba32: true liloconfig/configuring_base: lilo/runme: = false liloconfig/wipe_old_liloconf: false liloconfig/activate_error: lilo/new-config: lilo/link2: liloconfig/maintitle: liloconfig/mbr_error: liloconfig/lilo_warning: liloconfig/no_changes: * lilo/add_large_memory: false liloconfig/liloconf_incompatible: lilo/bad_bitmap: * lilo/install-note: lilo/upgrade: liloconfig/liloconf_exists: lilo/link1: liloconfig/use_current_lilo: true liloconfig/instruction: * lilo/config: liloconfig/select_bitmap: /boot/coffee.bmp liloconfig/lilo_error: * lilo/old-config: liloconfig/odd_fstab: liloconfig/install_from_root_device: true liloconfig/make_active_partition: true liloconfig/install_mbr: false -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
