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

Bug#354334: marked as done (udev removal should remake initrd)

Your message dated Mon, 20 Mar 2006 10:31:40 +0100
with message-id <20060320093140.GA20334@nancy>
and subject line Bug#354334: udev removal should remake initrd
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: udev
Severity: important


after installing udev, my computer randomly fails to boot and displayed
a busybox.

For that reason I decided to install yaird and remove udev.
But when removing udev, the initrd wasn't remade and still contained some
udev scripts.
It make the system unbootable.

When udev is removed it should remake the initrd or display a big
warning asking the user that it should remade the initrd.



-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.15
Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro (charmap=ISO-8859-15)

--- End Message ---
--- Begin Message ---
On Mon, 20 Mar 2006, matthieu castet wrote:

> My bug was about udev or initrd tools not clearing the initrd image or 
> displaying a BIG warning that the user need to rebuild the initrd when 
> he choose another initrd tools.

initramfs-tools will never clear initrd images in postrm.
making your system unbootable by default seems not like a good idea.
> For example if I switch from initramfs-tools to yaird, nothing will tell 
> me that I have to rebuild the initrd image before rebooting.

initrd-tools never touched the generated initrd.img for good reasons.
they are created by the postinst of linux-image
afaik an removal of the relative linux-image removes also its initrd.img.
if you want to switch from initramfs generator you need to explictly
dpkg-reconfigure linux-image-2.6.16-1-686

this will pick up your installed initramfs generator and check if said
initramfs generator can do so for the kernel version.
> The fact that udev/initramfs-tools didn't work was another story. And I 
> am sorry, but I can't retest this soon.
> IIRC there was missing udev script in the initrd image and sometimes 
> udev failed to get /dev/console (or something like that).

closing this bug report as there is no way for initramfs-tools
to blindly/randomly poke into linux-images generated initrd.img
it should be pretty clear that the initrd.img does not appartain
initramfs-tools itself, which just generates it on demand for
your linux image.


--- End Message ---

Reply to: