Re: asynchronous calls an the lack of --wait-for-completion options (e.g. modprobe, losetup, cryptsetup)
From: Kay Sievers
Date: Tue Jun 23 2009 - 07:35:34 EST
On Mon, Jun 22, 2009 at 14:08, Alexander Holler<holler@xxxxxxxxxxxxx> wrote:
> On 20.06.2009 21:20, Kay Sievers wrote:
> Anyway, I still think, that the creation of the device-node is (seen from a
> user-point) part of the module-initialization or part of the operation of
> the userland-tool (like modprobe, losetup or cryptsetup). So in my point of
> view, they should at least offer an option to wait until udev finished that
> operation and should not rely on the user to call udevadm.
That would be all solved properly by "devtmpfs":
You might want to talk to the people who are delaying its adoption.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/