1 |
Am Samstag 20 Juni 2009 09:37:24 schrieb Mike Kazantsev: |
2 |
|
3 |
> Dirk Heinrichs <dirk.heinrichs@××××××.de> wrote: |
4 |
> > > I believe there's "after device-mapper" line already in lvm-2.02.45, so |
5 |
> > > it should run fine, but as an additional precaution I have dm-crypt |
6 |
> > > script at sysinit runlevel, which starts device-mapper and dm-crypt |
7 |
> > > before lvm or even it's runlevel (boot). |
8 |
> > |
9 |
> > That's not needed, it should be sufficient to have them all in the boot |
10 |
> > runlevel: |
11 |
> |
12 |
> So LVM would start before dmcrypt? Great. |
13 |
|
14 |
Yes. |
15 |
|
16 |
> > > It makes sense for me, since some lvm pv's (not root) are actually on |
17 |
> > > encrypted partitions, although I mount these even earlier, but should |
18 |
> > > initrd become incompatible w/ latest kernel, dm-crypt should do the job |
19 |
> > > instead. |
20 |
> > |
21 |
> > No, it does not make sense. You don't even need an initrd. |
22 |
> |
23 |
> I do, but mainly for other purposes. |
24 |
|
25 |
Which? |
26 |
|
27 |
> Mounting encrypted partitions from there is a bonus and while root is |
28 |
> not encrypted (although it doesn't even holds most configuration |
29 |
> from /etc) it is an LVM volume. |
30 |
|
31 |
> Can linux boot from lvm root w/o initrd these days? |
32 |
|
33 |
Yes, it always could. As long as /boot is a separate partition one can put the |
34 |
same stuff into it. Much simpler to setup. |
35 |
|
36 |
Bye... |
37 |
|
38 |
Dirk |