LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   missing udevadm in initrd on slackware-13rc1 (http://www.linuxquestions.org/questions/slackware-14/missing-udevadm-in-initrd-on-slackware-13rc1-740242/)

bonaire 07-15-2009 09:37 AM

missing udevadm in initrd on slackware-13rc1
 
Hello,

im using a luks encrypted slackware-13rc1 installation on my netbook.
After unlocking my /, i get can see the messages:

Code:

sh: /sbin/udevadm: not found
Key slot 0 unlocked.
sh: /sbin/udevadm: not found
Command success.

My mkinitrd.conf looks as follows
Code:

SOURCE_TREE="/boot/initrd-tree"
CLEAR_TREE="1"
OUTPUT_IMAGE="/boot/initrd.gz"
KERNEL_VERSION="2.6.30.1-smp"
KEYMAP="de-latin1-nodeadkeys"
MODULE_LIST="ehci_hcd:uhci_hcd:usb_storage:exportfs:xfs:ext2"
LUKSDEV="/dev/mapper/vg-root"
ROOTDEV="crypt-vg-root"
ROOTFS="xfs"
LVM="1"

The initrd was built with mkinitrd -F
My /boot is ext2 formatted.
My / is xfs formatted.

The boot process works totally normal after these messages. So my question is:
Is this a configuration failure?
Is this relevant in any kind?
Is this a bug in mkinitrd?


cu

rworkman 07-15-2009 01:37 PM

It's a harmless "error" caused by a faulty assumption made by upstream cryptsetup; I've got a mkinitrd patch queud for it, but since it's ultimately harmless, it's a bit low on the priority ladder right now.

bonaire 07-15-2009 04:25 PM

Ok, i just mentioned it because it was the only error i found which is maybe caused by slackware itself ;) I love it.


All times are GMT -5. The time now is 06:01 PM.