From: Robert Hancock <hancockrwd@gmail.com>
To: Alexander Holler <holler@ahsoftware.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: asynchronous calls an the lack of --wait-for-completion options (e.g. modprobe, losetup, cryptsetup)
Date: Thu, 18 Jun 2009 18:52:50 -0600 [thread overview]
Message-ID: <4A3AE162.7040407@gmail.com> (raw)
In-Reply-To: <4A38F229.70504@ahsoftware.de>
On 06/17/2009 07:39 AM, Alexander Holler wrote:
> Hello,
>
> during the last kernel versions I've got more and more problems with
> scripts which are calling modprobe, losetup or e.g. cryptsetup.
>
> The problem is that when I'm e.g. calling modprobe loop, loop might not
> has finished it's initialization, when modprobe returns.
It will have. Just that udev won't have received the events and created
the device node yet. So the solution would likely be on the udev side..
next prev parent reply other threads:[~2009-06-19 0:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 13:39 asynchronous calls an the lack of --wait-for-completion options (e.g. modprobe, losetup, cryptsetup) Alexander Holler
2009-06-19 0:52 ` Robert Hancock [this message]
2009-06-20 19:20 ` Kay Sievers
2009-06-22 12:08 ` Alexander Holler
2009-06-23 11:35 ` Kay Sievers
2009-06-23 16:01 ` Alan Cox
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=4A3AE162.7040407@gmail.com \
--to=hancockrwd@gmail.com \
--cc=holler@ahsoftware.de \
--cc=linux-kernel@vger.kernel.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