From: "Thomas Bächler" <thomas@archlinux.org>
To: Milan Broz <gmazyland@gmail.com>
Cc: dm-crypt@saout.de, ebelcrom ebelcrom <ebelcrom@googlemail.com>,
Bryan Kadzban <bryan@kadzban.is-a-geek.net>
Subject: Re: [dm-crypt] ing rootfs without initramfs
Date: Sun, 21 Jul 2013 11:01:14 +0200 [thread overview]
Message-ID: <51EBA35A.8000602@archlinux.org> (raw)
In-Reply-To: <51EBA015.10409@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 717 bytes --]
Am 21.07.2013 10:47, schrieb Milan Broz:
> I think using some initramfs is the only solution now for mapping
> encrypted root fs (for now).
I would remove "for now" from your statement. Unlocking the volume from
kernel code itself requires that the kernel learns how to ask for
passphrases and/or find key files, do LUKS header processing and accept
device-mapper parameters in some way.
This is very complicated to do in kernel code and adds tons of kernel
code for tasks that do not belong into the kernel. Such patches will
never be accepted upstream, since there is a more flexible and less
error-prone mechanism to solve the problem (it's called "initramfs", if
you didn't guess it already).
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2013-07-21 9:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-20 19:36 [dm-crypt] ing rootfs without initramfs ebelcrom ebelcrom
2013-07-20 20:06 ` Milan Broz
2013-07-21 5:40 ` Bryan Kadzban
2013-07-21 8:47 ` Milan Broz
2013-07-21 9:01 ` Thomas Bächler [this message]
2013-07-21 12:27 ` Milan Broz
2013-07-22 3:51 ` Will Drewry
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=51EBA35A.8000602@archlinux.org \
--to=thomas@archlinux.org \
--cc=bryan@kadzban.is-a-geek.net \
--cc=dm-crypt@saout.de \
--cc=ebelcrom@googlemail.com \
--cc=gmazyland@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.