Your message dated Sun, 29 Mar 2009 18:35:34 +0200
with message-id <20090329163533.gr7...@stro.at>
and subject line Re: firmware-bnx2: doesn't rebuild all initrds
has caused the Debian Bug report #493863,
regarding firmware-bnx2: doesn't rebuild all initrds
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 ow...@bugs.debian.org
immediately.)
--
493863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=493863
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firmware-bnx2
Version: 0.4+etchnhalf.1
Severity: important
I installed the etchnhalf kernel, rebooted only to find out that I had
not network, booted the old kernel again and installed firmware-bnx2:
| thelma:~# apt-get install firmware-bnx2
| Reading package lists... Done
| Building dependency tree... Done
| The following NEW packages will be installed:
| firmware-bnx2
| 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
| Need to get 104kB of archives.
| After unpacking 279kB of additional disk space will be used.
| Get:1 http://mirror.came.sbg.ac.at etch/non-free firmware-bnx2
0.4+etchnhalf.1 [104kB]
| Fetched 104kB in 0s (1818kB/s)
| Selecting previously deselected package firmware-bnx2.
| (Reading database ... 62627 files and directories currently installed.)
| Unpacking firmware-bnx2 (from .../firmware-bnx2_0.4+etchnhalf.1_all.deb) ...
| Setting up firmware-bnx2 (0.4+etchnhalf.1) ...
| update-initramfs: Generating /boot/initrd.img-2.6.18-5-amd64
Note how it doesn't rebuild the 2.6.24 etchnhalf initrd. Needless to say
the system still didn't properly boot, only purging and reinstalling the
linux-image-2.6.24-etchnhalf.1-amd64 did the trick.
Maybe the firmware-bnx2 package should do "update-initramfs -u -k all"
instead of just "update-initramfs -u".
--- End Message ---
--- Begin Message ---
> Maybe the firmware-bnx2 package should do "update-initramfs -u -k all"
> instead of just "update-initramfs -u".
no.
it was explicitly asked that packages in postinst only update
the newest initramfs (which can be the one which has the symlink).
yes conservative people want to have least possible "damage" policy,
but it is easily overridable.
if you want to have all initramfs updated set in
/etc/initramfs-tools/update-initramfs.conf
update_initramfs=all
--
maks
--- End Message ---
