All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: ebelcrom ebelcrom <ebelcrom@googlemail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] ing rootfs without initramfs
Date: Sat, 20 Jul 2013 22:06:12 +0200	[thread overview]
Message-ID: <51EAEDB4.1090407@gmail.com> (raw)
In-Reply-To: <CACxrqpCg4zP-G0ufRz2rSafqqX1mw=5JjSWw=nfjaQ0QEw-CBQ@mail.gmail.com>

On 07/20/2013 09:36 PM, ebelcrom ebelcrom wrote:

> I played around with dm-crypt without using initramfs for
> en-/decryption of my root file system. The rootfs is encrypted plain
> with cryptsetup and the key is stored at the disk containing the
> rootfs between MBR and the partition. The kernel parameter given to
> it from the bootloader is configured as it should be (cryptdevice,
> cryptkey, root mapper). The disk driver (loaded before) is built-in
> as well as dm-crypt (loaded after). The message I got at boot time is
> this (cr_rootfs is the encrypted rootfs):
> 
> VFS: Cannot open root device "mapper/cr_rootfs" or
> unknown-block(0,0)
> 
> According to some hints in the web there is no need to have an
> initramfs. Is that true? If yes what are the steps to get there and
> what should I keep into account?

I think the only possibility is to use GRUB2 which should understand
LUKS directly and boot from it. (Not sure about plain dmcrypt device).

I do not think you can create device-mapper block device without
initramfs (there were some patches to add some kernel options
but IIRC it never reached upstream).

Milan

  reply	other threads:[~2013-07-20 20: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 [this message]
2013-07-21  5:40   ` Bryan Kadzban
2013-07-21  8:47     ` Milan Broz
2013-07-21  9:01       ` Thomas Bächler
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=51EAEDB4.1090407@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=dm-crypt@saout.de \
    --cc=ebelcrom@googlemail.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.