> 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. But the word 'sysinit' doesn't appear even once in the entire rc.log. Another clue? FWIW I stopped dm-crypt from being loaded to test whether I really need it. Makes no difference. mw
