From: Mike Kazantsev <mk.fraggod@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] lvm problem -- is timing?
Date: Sat, 20 Jun 2009 13:37:24 +0600 [thread overview]
Message-ID: <20090620133724.58b4e872@coercion> (raw)
In-Reply-To: <200906200908.10610.dirk.heinrichs@online.de>
[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]
On Sat, 20 Jun 2009 09:08:05 +0200
Dirk Heinrichs <dirk.heinrichs@online.de> wrote:
> > I believe there's "after device-mapper" line already in lvm-2.02.45, so
> > it should run fine, but as an additional precaution I have dm-crypt
> > script at sysinit runlevel, which starts device-mapper and dm-crypt
> > before lvm or even it's runlevel (boot).
>
> That's not needed, it should be sufficient to have them all in the boot
> runlevel:
So LVM would start before dmcrypt? Great.
> > It makes sense for me, since some lvm pv's (not root) are actually on
> > encrypted partitions, although I mount these even earlier, but should
> > initrd become incompatible w/ latest kernel, dm-crypt should do the job
> > instead.
>
> No, it does not make sense. You don't even need an initrd.
I do, but mainly for other purposes.
Mounting encrypted partitions from there is a bonus and while root is
not encrypted (although it doesn't even holds most configuration
from /etc) it is an LVM volume.
Can linux boot from lvm root w/o initrd these days?
--
Mike Kazantsev // fraggod.net
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-06-20 7:40 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-20 4:15 [gentoo-user] lvm problem -- is timing? Maxim Wexler
2009-06-20 5:33 ` Mike Kazantsev
2009-06-20 7:08 ` Dirk Heinrichs
2009-06-20 7:37 ` Mike Kazantsev [this message]
2009-06-20 9:01 ` Dirk Heinrichs
2009-06-20 11:56 ` Mike Kazantsev
2009-06-20 12:46 ` Dirk Heinrichs
2009-06-20 19:23 ` Maxim Wexler
2009-06-20 20:26 ` Dirk Heinrichs
2009-06-20 20:34 ` Dirk Heinrichs
2009-06-20 19:14 ` Maxim Wexler
2009-06-20 20:23 ` Dirk Heinrichs
2009-06-20 20:48 ` Dirk Heinrichs
2009-06-20 23:51 ` Maxim Wexler
2009-06-21 7:57 ` Dirk Heinrichs
2009-06-21 21:16 ` Maxim Wexler
2009-06-21 21:32 ` Maxim Wexler
2009-06-21 21:49 ` Neil Bothwick
2009-06-21 22:17 ` Ian Lee
2009-06-22 1:20 ` Maxim Wexler
2009-06-22 16:43 ` Dirk Heinrichs
2009-06-22 17:23 ` Maxim Wexler
2009-06-22 1:13 ` Maxim Wexler
2009-06-22 7:12 ` Neil Bothwick
2009-06-22 17:42 ` Maxim Wexler
2009-06-22 22:20 ` Neil Bothwick
2009-06-22 18:09 ` Maxim Wexler
2009-06-22 22:25 ` Neil Bothwick
2009-06-23 2:12 ` Maxim Wexler
2009-06-23 7:32 ` Neil Bothwick
2009-06-23 19:15 ` Maxim Wexler
2009-06-23 21:09 ` Alan McKinnon
2009-06-23 21:36 ` Neil Bothwick
2009-06-23 21:59 ` Maxim Wexler
2009-06-23 22:03 ` Neil Bothwick
2009-06-24 20:10 ` Maxim Wexler
2009-06-22 16:49 ` Dirk Heinrichs
2009-06-22 17:33 ` Maxim Wexler
2009-06-22 22:21 ` Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090620133724.58b4e872@coercion \
--to=mk.fraggod@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox