public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Kacper Kopczyński" <capsel@matrix.inten.pl>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] LVM on LUKS
Date: Sat, 7 Aug 2010 13:29:07 +0200	[thread overview]
Message-ID: <20100807132907.7bd9164c@matrix.inten.pl> (raw)
In-Reply-To: <4C5D2BF2.4010903@f_philipp.fastmail.net>

Dnia 2010-08-07, o godz. 11:48:34
Florian Philipp <lists@f_philipp.fastmail.net> napisał(a):

> Hi list!
> 
> I'm building a new Gentoo system (notebook) and want to rearrange a
> few things. I thought it would be good to have the following layout:
> 
>  - boot on a normal partition
>  - root on a normal partition
>  - one big encrypted partition (dmcrypt / LUKS)
>  - on that partition an LVM volume group
>  - on that volume group all stuff not necessary for booting: home,
> var, tmp, etc.
> 
> AFAIK, the Gentoo boot process is organized so that LVM gets stated
> before dmcrypt is started. I would need it vice versa.
> 
> Is that possible with baselayout-1? Do I need to switch to
> baselayout-2?
> 
> Thanks in advance!
> Florian Philipp
> 

I've made my own initramfs to boot.

/boot	is a separate partition with ext2, grub, bzImage and
	initramfs
/	is ext4 on logical volume on encrypted container
	[ext4:lvm:luks:sda2]
swap	is on another logical volume, next to /

I used two links as hints to build it:
http://jootamam.net/howto-initramfs-image.htm
http://jootamam.net/howto-basic-cryptsetup.htm

It's important to have all libraries copied to initramfs or to make all
binaries static (ldd). Some time ago I had dropbear in initramfs to
help booting headless server. Watch out for pivot_root restriction of
PID == 1.

-- 
Kacper Kopczyński



  parent reply	other threads:[~2010-08-07 11:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-07  9:48 [gentoo-user] LVM on LUKS Florian Philipp
2010-08-07 11:11 ` Alex Schuster
2010-08-07 11:29 ` Kacper Kopczyński [this message]
2010-08-07 11:30 ` Neil Bothwick
2010-08-11 17:46 ` Florian Philipp

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=20100807132907.7bd9164c@matrix.inten.pl \
    --to=capsel@matrix.inten.pl \
    --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