Warning not updating lilo etclilo conf not found

Versions of packages lilo suggests: pn lilo-doc (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: liloconfig/maintitle: liloconfig/mbr_error: liloconfig/lilo_warning: liloconfig/no_changes: lilo/add_large_memory: true liloconfig/liloconf_incompatible: lilo/bad_bitmap: lilo/upgrade: liloconfig/liloconf_exists: liloconfig/use_current_lilo: true liloconfig/instruction: liloconfig/select_bitmap: /boot/liloconfig/lilo_error: liloconfig/odd_fstab: liloconfig/install_from_root_device: true liloconfig/make_active_partition: true liloconfig/install_mbr: false -- Moshe Yudkowsky * [email protected]* "Morality is alright, but what about dividends?" -- Kaiser Willhem II ("The Sudden") seen in the following output: This is ultimately a bug in the new policy for boot loaders. [...] It's not supposed to do this; I think you must be mistaken. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.Commit interval 5 seconds [126468.691223] EXT3-fs (sdb1): using internal journal [126468.691225] EXT3-fs (sdb1): recovery complete [126468.694526] EXT3-fs (sdb1): mounted filesystem with ordered data mode [173828.541718] sdb: detected capacity change from 4009549824 to 0 [179577.977554] sd 6:0:0:0: [sdb] 7831152 512-byte logical blocks: (4.00 GB/3.73 Gi B) [179577.994839] sdb: sdb1 [179578.376157] kjournald starting.

warning not updating lilo etclilo conf not found-37warning not updating lilo etclilo conf not found-20warning not updating lilo etclilo conf not found-12

I didn't consider (and no-one pointed out) that a boot loader package might be installed even though the boot loader is not installed. diff -u lilo-22.8/debian/lilo.kernel-postrm lilo-22.8/debian/lilo.kernel-postrm --- lilo-22.8/debian/lilo.kernel-postrm lilo-22.8/debian/lilo.kernel-postrm @@ -2,2 2,4 @@ -# Do not abort kernel removal in case of error -lilo &2 "Warning: Not updating LILO; /etc/not found" fi diff -u lilo-22.8/debian/lilo.initramfs-post-update lilo-22.8/debian/lilo.initramfs-post-update --- lilo-22.8/debian/lilo.initramfs-post-update lilo-22.8/debian/lilo.initramfs-post-update @@ -7,5 7,9 @@ ;; *) - lilo &2 "Warning: Not updating LILO; /etc/not found" fi ;; esac diff -u lilo-22.8/debian/changelog lilo-22.8/debian/changelog --- lilo-22.8/debian/changelog lilo-22.8/debian/changelog @@ -1,3 1,11 @@ lilo (.8-8.3) unstable; urgency=high * Non-maintainer upload.

* Change kernel and initramfs hook scripts to do nothing if does not exist (Closes: #594479) -- Ben Hutchings Source: lilo Source-Version: .8-8.3 We believe that the bug you reported is fixed in the latest version of lilo, which is due to be installed in the Debian FTP archive: lilo-doc_22.8-8.3_to main/l/lilo/lilo-doc_22.8-8.3_lilo_22.8-8.3gz to main/l/lilo/lilo_22.8-8.3gz lilo_22.8-8.3to main/l/lilo/lilo_22.8-8.3lilo_22.8-8.3_i386to main/l/lilo/lilo_22.8-8.3_i386A summary of the changes between this version and the previous one is attached.

With a Compact Flash disk, for instance, containing the Linux filesystem and mounted on a desktop Linux development machine, a few hoops need to be jumped through in order to install the bootloader onto the Compact Flash card.

This method is usually necessary when there isn't already a bootable disk for the embedded machine.

AFAICT, there's no /etc/kernel policy that selects between grub and lilo, so I'm not certain how to resolve this problem -- how to leave both packages installed.

I should also mention that as far as I can recall, this same lilo update removed /etc/-- I recall reading a message.If the kernel name changed, the configuration file will need to be modified to suit before reinstalling LILO.See Configuring LILO for more information on how to do this.Two sets of directions for doing this are given here.The first set of directions is generic, and will work for desktop Linux distributions which do not include an automounter or have an automounter which doesn't interfere with the process. The following steps will need to be performed to install LILO onto a removable drive: For simpler systems without an automounter, or with an automounter that doesn't try to protect the user from possibly malicious code, follow these directions. [126468.154762] sd 6:0:0:0: [sdb] 7831152 512-byte logical blocks: (4.00 GB/3.73 Gi B) [126468.182196] sdb: sdb1 [126468.688061] kjournald starting.Before LILO can be used to boot a system, it must be installed onto the boot device.

Tags: , ,