mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Mr Dash Four <mr.dash.four-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
To: initramfs <initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: crypt-cleanup.sh question
Date: Tue, 26 Oct 2010 15:37:53 +0100	[thread overview]
Message-ID: <4CC6E7C1.1050703@googlemail.com> (raw)
In-Reply-To: <4CC6C571.8010406-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>


> What is the rationale behind closing all /dev/mapper/luks-* devices 
> which are not 'busy' in this shell script? Why would they have to be 
> 'busy' (I presume already mapped) to be left open?
>
> I am asking this because when the smartcard module opens a LUKS drive 
> (not root - '/') - this drive later to be mapped from the actual root 
> /etc/fstab file as '/dev/mapper/luks-XXX /some/directory' - this 
> operation does not succeed and I presume crypt-cleanup.sh closes it up 
> before the actual root can get it and therefore it cannot be mapped.
Further to the above, I was able to verify that the above script is 
indeed to blame for closing LUKS partitions. The only 'busy' partition 
at the time crypt-cleanup.sh runs is the root (/sysroot) so I don't see 
how a LUKS partition (other than root) specified at the kernel command 
line could be opened, unless I am missing something obvious...

  parent reply	other threads:[~2010-10-26 14:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-26 12:11 crypt-cleanup.sh question Mr Dash Four
     [not found] ` <4CC6C571.8010406-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2010-10-26 14:37   ` Mr Dash Four [this message]
     [not found]     ` <4CC7F15C.7090600@redhat.com>
     [not found]       ` <4CC7F15C.7090600-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-10-27 12:07         ` Mr Dash Four
     [not found]           ` <4CC815E4.4060705-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2010-10-27 13:08             ` Harald Hoyer
     [not found]               ` <4CC82448.80403-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-10-27 13:17                 ` Mr Dash Four
     [not found]                   ` <4CC82652.3090500-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2010-10-27 13:37                     ` Harald Hoyer
     [not found]                       ` <4CC82B0B.30208-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-10-27 14:16                         ` Mr Dash Four
     [not found]                           ` <4CC83425.2010706-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2010-10-27 14:27                             ` Amadeusz Żołnowski
2010-10-27 15:08                             ` 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=4CC6E7C1.1050703@googlemail.com \
    --to=mr.dash.four-gm/ye1e23mwn+bqq9rbeug@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@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