Your message dated Thu, 06 Nov 2008 10:36:22 +0900
with message-id <[EMAIL PROTECTED]>
and subject line Re: lilo: 504464: more info
has caused the Debian Bug report #504464,
regarding lilo: Post-install fails if large_memory is not set and no
initramfs/initrd image is used
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
504464: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504464
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
On Wed, 2008-11-05 at 16:48 +0100, Michael Guntsche wrote:
> Of course if you KNOW that this is okay, you can just call lilo manually
> afterwards and it won't complain.
So do that.
> What about checking for the existence of an /initrd.img only if it is
> configured in the conf file?
Requires parsing the config file. lilo itself doesn't seem to provide
any provision for this so it will require very fragile code to somehow
guess if an initrd is used. I don't think it is worth doing since the
aim of the warnings is to make the sysadmin aware of the issue in the
case where the debconf note is not shown. When the sysadmin is using
lilo as a bootloader I would expect them to be able to read
README.Debian and act accordingly and ignore the warnings if there is no
problem on their system.
> Right now lilo is not called at all, which is a more serious problem in my
> opinion since this did not happen with earlier versions.
Your debconf settings say that you do not want lilo to be run.
--
bye,
pabs
http://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
--- End Message ---
