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

Re: udev strangeness in Sid?



Peter Hirdina wrote:
Hi,


I then found out that the problem is absent when I create my initrd with
yaird instead of mkinitramfs. The yaird-generated initrd is also much
smaller than the one from mkinitramfs (939 KB vs 2.1 MB).


I had the same problem. I checked the generated initrd file and noticed
that the programs udevd moans about here are missing in the initrd file.
I put this at the end of /usr/share/initramfs-tools/hooks/udev:

  mkdir $DESTDIR/lib/udev/
  cp /lib/udev/hotplug.functions $DESTDIR/lib/udev/
  +copy_exec /lib/udev/ata_id /lib/udev
  +copy_exec /lib/udev/cdrom_id /lib/udev
  +copy_exec /lib/udev/edd_id /lib/udev
  +copy_exec /lib/udev/firmware.agent /lib/udev
  +copy_exec /lib/udev/ide-devfs.sh /lib/udev
  +copy_exec /lib/udev/ide.agent /lib/udev
  +copy_exec /lib/udev/logger.agent /lib/udev
  +copy_exec /lib/udev/modalias_ieee1394 /lib/udev
  +copy_exec /lib/udev/modalias_serio /lib/udev
  +copy_exec /lib/udev/net.agent /lib/udev
  +copy_exec /lib/udev/path_id /lib/udev
  +copy_exec /lib/udev/raid-devfs.sh /lib/udev
  +copy_exec /lib/udev/scsi-devfs.sh /lib/udev
  +copy_exec /lib/udev/scsi-re-add /lib/udev
  +copy_exec /lib/udev/scsi_id /lib/udev
  +copy_exec /lib/udev/udev_run_devd /lib/udev
  +copy_exec /lib/udev/udev_run_hotplugd /lib/udev
  copy_exec /lib/udev/udevsynthesize /lib/udev
  +copy_exec /lib/udev/usb_id /lib/udev
  copy_exec /lib/udev/vio.agent /lib/udev
  +copy_exec /lib/udev/vol_id /lib/udev

Regenerated the initrd file, and the errors are gone.

Alright, so that's the proper way to solve it. I was in a hurry, therefore I
just renamed both /usr/sbin/mkinitramfs and /usr/sbin/mkinitrd and then I did a
dpkg-reconfigure on my linux-image package. This resulted in yaird being used,
but it is of course an extremely ugly hack. I guess I should finally learn the
correct usage of the various initrd generators.

Thanks a lot for the information.

Regards,
           Florian



Reply to: