Your message dated Tue, 13 Jun 2023 04:48:16 +0000
with message-id <[email protected]>
and subject line Bug#1037326: Removed package(s) from unstable
has caused the Debian Bug report #849524,
regarding lilo: lock, lilo -R and fallback= broken, only display first letter 
and hang on boot
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.)


-- 
849524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849524
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lilo
Version: 1:24.1-1
Severity: normal

Dear Maintainer,

I have a rather old (flaky, and hard to access) server which uses the
fallback= mechanism in lilo.conf to round-robin between various boot
configs, which worked fine in the past.

I don't know when exactly I tested the mechanism last, but it might have
been before the upgrade to jessie.

Recently, I upgraded the debian kernel and re-ran lilo, then tried to test
the fallback mechanism.

The first boot was normal, the second boot (which should switch to the
first fallback, didn't, lilo did hang like this:

   LILO 24.1 boot: p

The "p" is the first letter of the fallback image name
("previous"). Booting again booted the default image, as if no fallback
was given (so not all was lost :).

After experimenting, neither fallback= nor lilo -R nor the lock option
work anymore - all of them lead to a display similar like the above and a
hang at boot, with only the first character of the image name displayed.

So, basically, doing this:

   lilo
   lilo -R gxpe

Leads to hang like this:

   LILO 24.1 boot: g

Or a lock use like this:

   boot: rescue-emdeb abc lock

Leads to a hang like this:

   LILO 24.1 boot: r

The (slightly cleaned-up to the essentials) lilo.conf looks like this:

   boot = "/dev/disk/by-id/ata-Hitachi_HDS722020ALA330_JK1130YAH69SMT"

   append = "root=/dev/disk/by-label/ROOT ..."

   delay = 50
   timeout = 100
   unattended
   serial = 2,115200n8

   lba32
   compact
   large-memory
   map=/boot/map

   default=default

   ### cycling through these:

   image=/boot/vmlinuz-3.16.0-4-amd64
      initrd=/boot/initrd.img-3.16.0-4-amd64
      label=default
      fallback=previous
      read-only
      addappend="..."

   image=/boot/vmlinuz-3.16.0-4-amd64
      initrd=/boot/initrd.img-3.16.0-4-amd64
      label=previous
      fallback=rescue
      read-only
      addappend="..."

   image = /boot/rescue-kernel
      label = rescue
      fallback = rescue-emdeb
      initrd = /boot/rescue-initrd

   image = /boot/rescue-emdeb-kernel
      label = rescue-emdeb
      fallback = gpxe
      initrd = /boot/rescue-emdeb-initrd

   image = /boot/rain.gpxe
      label = gpxe
      fallback = default

When I run a "lilo" and keep the output of "strings /boot/map" and then
run "lilo -R rescue" and compare it with the saved stings output, then I
can see an additional "rescue" string. Likewise, the commandline I enter
with lock ends up in /boot/map (e.g. "rescue abc lock"), so storing the
commandline seems to work, but booting form it does not.

Thanks for still maintaining lilo, btw., it's much appreciated for its
stability and options such as fallback.

Greetings,
Marc

--- End Message ---
--- Begin Message ---
Version: 1:24.2-5.1+rm

Dear submitter,

as the package lilo has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1037326

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to