mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Alexander Tsoy <alexander-EP/B3+myoZc@public.gmane.org>
To: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Thomas Renninger <trenn-l3A5Bk7waGM@public.gmane.org>,
	initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Intend of hostonly-cmdline?
Date: Wed, 7 May 2014 17:15:27 +0400	[thread overview]
Message-ID: <20140507171527.2d826560@work.puleglot> (raw)
In-Reply-To: <536A22C9.8000007-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

В Wed, 07 May 2014 14:10:49 +0200
Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> пишет:

> On 07.05.2014 14:08, Harald Hoyer wrote:
> > On 07.05.2014 13:47, Alexander Tsoy wrote:
> >> Actually hostonly-cmdline is partially broken with systemd in
> >> initramfs. For example systemd-cryptsetup-generator does not
> >> read /etc/cmdline.d/*.conf files, so rd.luks* parameters must be
> >> appended to kernel cmdline anyway.
> >>
> > 
> > True! Good point!
> > Although /etc/crypttab is included with hostonly.
> > 
> 
> Ah, oh.. I forgot, dracut *does* use rd.luks.uuid from the kernel command line
> and creates /etc/crypttab lines from it in the initramfs.
> So basically it *should* work with systemd.

This doesn't work with full disk encryption. Unit file does not get
generated and I see this message:

[    7.142993] testhost dracut-initqueue[202]: Failed to start systemd-cryptsetup@luks\x2d342d2414\x2d159c\x2d48d7\x2da0b7\x2d5b59fa6e27a5.service: Unit 
systemd-cryptsetup@luks\x2d342d2414\x2d159c\x2d48d7\x2da0b7\x2d5b59fa6e27a5.service failed to load: No such file or directory.

Probably this is because crypt-run-generator get executed from udev
rules only if *both* of the following conditions are true:
- there is no rd.luks.uuid parameter in both cmdline
and /etc/cmdline.d/*.conf
- rd.auto is enabled

-- 
Alexander Tsoy

  parent reply	other threads:[~2014-05-07 13:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07 11:12 Intend of hostonly-cmdline? Thomas Renninger
2014-05-07 11:32 ` Harald Hoyer
     [not found]   ` <536A19D7.2010405-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-05-07 11:47     ` Alexander Tsoy
     [not found]       ` <20140507154733.386369cd-d/9N6kaejYfpx9ONITL1FA@public.gmane.org>
2014-05-07 12:08         ` Harald Hoyer
     [not found]           ` <536A2222.50606-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-05-07 12:10             ` Harald Hoyer
     [not found]               ` <536A22C9.8000007-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-05-07 13:15                 ` Alexander Tsoy [this message]
     [not found]                   ` <20140507171527.2d826560-d/9N6kaejYfpx9ONITL1FA@public.gmane.org>
2014-05-08 13:54                     ` Alexander Tsoy
     [not found]                       ` <20140508175412.2386aa29-d/9N6kaejYfpx9ONITL1FA@public.gmane.org>
2014-05-13 19:26                         ` Alexander Tsoy
2014-05-07 13:40     ` Thomas Renninger
2014-05-07 13:48       ` Harald Hoyer

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=20140507171527.2d826560@work.puleglot \
    --to=alexander-ep/b3+myozc@public.gmane.org \
    --cc=harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=trenn-l3A5Bk7waGM@public.gmane.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