| 1 |
Am Samstag 20 Juni 2009 21:14:35 schrieb Maxim Wexler: |
| 2 |
> > Guess you can do the same, at least if you don't have dm-crypt |
| 3 |
> > mappings, or you can try adding device-mapper to sysinit level directly. |
| 4 |
> > |
| 5 |
> > |
| 6 |
> > Here's my boot sequence (from rc.log): |
| 7 |
> > |
| 8 |
> > |
| 9 |
> > rc sysinit logging started at Fri Jun 12 04:24:55 2009 |
| 10 |
> |
| 11 |
> No good. rc-update shows udev, devfs, dmesg, device-mapper in sysinit |
| 12 |
> runlevel. |
| 13 |
|
| 14 |
device-mapper is wrong, there. |
| 15 |
|
| 16 |
# ll /etc/runlevels/sysinit |
| 17 |
insgesamt 0 |
| 18 |
lrwxrwxrwx 1 root root 17 28. Dez 14:03 devfs -> /etc/init.d/devfs* |
| 19 |
lrwxrwxrwx 1 root root 17 28. Dez 14:03 dmesg -> /etc/init.d/dmesg* |
| 20 |
lrwxrwxrwx 1 root root 16 28. Dez 17:09 udev -> /etc/init.d/udev* |
| 21 |
|
| 22 |
It belongs into boot, together with dmcrypt and lvm. |
| 23 |
|
| 24 |
Bye... |
| 25 |
|
| 26 |
Dirk |
Archives