Am Samstag 20 Juni 2009 21:14:35 schrieb Maxim Wexler: > > Guess you can do the same, at least if you don't have dm-crypt > > mappings, or you can try adding device-mapper to sysinit level directly. > > > > > > Here's my boot sequence (from rc.log): > > > > > > rc sysinit logging started at Fri Jun 12 04:24:55 2009 > > No good. rc-update shows udev, devfs, dmesg, device-mapper in sysinit > runlevel.
device-mapper is wrong, there.
# ll /etc/runlevels/sysinit
insgesamt 0
lrwxrwxrwx 1 root root 17 28. Dez 14:03 devfs -> /etc/init.d/devfs*
lrwxrwxrwx 1 root root 17 28. Dez 14:03 dmesg -> /etc/init.d/dmesg*
lrwxrwxrwx 1 root root 16 28. Dez 17:09 udev -> /etc/init.d/udev*
It belongs into boot, together with dmcrypt and lvm.
Bye...
Dirk
signature.asc
Description: This is a digitally signed message part.
