Bug#727708: systemd status when using multiple block device layers (MD/LVM/dm-crypt) below the root-fs

To: 727708@bugs.debian.org
Subject: Bug#727708: systemd status when using multiple block device layers (MD/LVM/dm-crypt) below the root-fs
From: Tollef Fog Heen <tfheen@err.no>
Date: Tue, 31 Dec 2013 21:07:18 +0100
Message-id: <[🔎] m2ppochjih.fsf@rahvafeir.err.no>
Mail-followup-to: debian-ctte@lists.debian.org
Reply-to: Tollef Fog Heen <tfheen@err.no>, 727708@bugs.debian.org
In-reply-to: <[🔎] 1388515557.26564.9.camel@heisenberg.scientia.net> (Christoph Anton Mitterer's message of "Tue, 31 Dec 2013 19:45:57 +0100")
References: <[🔎] 1388515557.26564.9.camel@heisenberg.scientia.net>

]] Christoph Anton Mitterer 

> Now that systemd could become default in Debian (well at least I favour
> it over upstream)... I started wondering how well it supports booting
> from a root fs on top of multiple block device layers?

That's handled by the initramfs where we currently don't use systemd.
(It's supported upstream to do so and we might eventually investigate
that, but I don't believe anybody has done any work on it for Debian.)

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are

Reply to:

Follow-Ups:
- Bug#727708: systemd status when using multiple block device layers (MD/LVM/dm-crypt) below the root-fs
  - From: Christoph Anton Mitterer <calestyo@scientia.net>

References:
- Bug#727708: systemd status when using multiple block device layers (MD/LVM/dm-crypt) below the root-fs
  - From: Christoph Anton Mitterer <calestyo@scientia.net>

Prev by Date: Bug#727708: loose ends for init system decision
Next by Date: Bug#727708: init system other points, and conclusion
Previous by thread: Bug#727708: systemd status when using multiple block device layers (MD/LVM/dm-crypt) below the root-fs
Next by thread: Bug#727708: systemd status when using multiple block device layers (MD/LVM/dm-crypt) below the root-fs
Index(es):
- Date
- Thread