Your message dated Sun, 5 Aug 2012 20:34:12 +0200
with message-id <20120805183412.ga27...@bongo.bofh.it>
and subject line Re: Bug#683953: udev: Dropping unix.ko from initrd makes
certain custom kernels unbootable
has caused the Debian Bug report #683953,
regarding udev: Dropping unix.ko from initrd makes certain custom kernels
unbootable
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.)
--
683953: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: udev
Version: 175-5
Severity: critical
Justification: breaks the whole system
Recently, bug #654282 was fixed by not attempting to include unix.ko in
initrd images. I run custom kernels with a high degree of modularization,
so a side effect of this change was that my systems became unbootable
without warning. Fortunately the postinst script only updates the initrd
image for the latest kernel, so I was able to boot into an earlier one and
downgrade udev back to 175-3.1.
I suggest checking for the presence of the unix.ko module when generating
the initrd and including it if necessary. Since manual_add_modules already
effectively checks for the presence of the module, perhaps it could return
a status code to let force_load know not to add the module in conf/modules.
If implementing the above is not possible, please check for the presence
of unix.ko (or, equivalently, CONFIG_UNIX=m) when upgrading udev and issue
a warning about unbootable system if it exists.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.2.1-core2 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages udev depends on:
ii debconf [debconf-2.0] 1.5.45
ii libc6 2.13-35
ii libselinux1 2.1.9-5
ii libudev0 175-5
ii lsb-base 4.1+Debian7
ii procps 1:3.3.3-2
ii util-linux 2.20.1-5.1
Versions of packages udev recommends:
ii pciutils 1:3.1.9-5
ii usbutils 1:005-3
udev suggests no packages.
-- debconf information excluded
--- End Message ---
--- Begin Message ---
On Aug 05, Mikko Rasa <t...@tdb.fi> wrote:
> Recently, bug #654282 was fixed by not attempting to include unix.ko in
> initrd images. I run custom kernels with a high degree of modularization,
The upstream udev maintainers clarified long ago than such
a configuration is not supported and I agree (along with the debian
kernel team).
There is no justification for building a kernel with CONFIG_UNIX=m, and
the requirement is documented in README.Debian.gz and README.gz.
> If implementing the above is not possible, please check for the presence
> of unix.ko (or, equivalently, CONFIG_UNIX=m) when upgrading udev and issue
> a warning about unbootable system if it exists.
I really do not want to spend all the time needed to manage a debconf
warning and its translations, unless there is a strong consensus that
I should do this for wheezy.
--
ciao,
Marco
signature.asc
Description: Digital signature
--- End Message ---
