[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#214058: marked as done (proposal: add optional initrd-images)

Your message dated Wed, 19 Mar 2014 22:42:59 +0100
with message-id <20140319214253.GD5789@mraw.org>
and subject line Re: Bug#214058: proposal: add optional initrd-images
has caused the Debian Bug report #214058,
regarding proposal: add optional initrd-images
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 owner@bugs.debian.org
immediately.)


-- 
214058: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=214058
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: lilo
Version: 1:22.5.7.2-3
Severity: wishlist
Tags: patch


Dear Maintainer!


After being bitten twice by forgetting to add an "initrd=" to an image,
I have solved that by adding additional, optional images containing the
default initrds. Like that:

image=/vmlinuz
        label=Linux
        read-only

image=/vmlinuz
        label=LinuxRD
        initrd=/initrd.img
        read-only
	optional

image=/vmlinuz.old
        label=LinuxOLD
        read-only
	optional

image=/vmlinuz.old
        label=LinuxRDOLD
        initrd=/initrd.img.old
        read-only
	optional

Putting these additional images into lilo.conf also obsoletes the initrd
question in kernel-package built kernel-images and makes lilo much more robust.
For people without initrd those images will be quietly ignored.


Thank you for your time and work,
David Schmitt

--- End Message ---
--- Begin Message --- 
David Schmitt <david@schmitt.edv-bus.at> (2014-03-19):
> If nobody on the lilo-installer team can answer this question by
> taking a quick look into his/her test setup, then it may be time to
> send the code to the attic?

I'm going to start with closing this bug report. Apparently lilo is
still maintained (at least uploaded), so if people have some more bugs,
they might be getting fixed.

Thanks for following up.

Mraw,
KiBi.

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: