Messages in this thread |  | | Date | Thu, 18 Jun 2009 18:52:50 -0600 | From | Robert Hancock <> | Subject | Re: asynchronous calls an the lack of --wait-for-completion options (e.g. modprobe, losetup, cryptsetup) |
| |
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..
|  |