On Tue, Jul 05, 2016 at 02:32:24PM -0400, Dale R. Worley wrote:
> Ruediger Meier <sweet_f_a@xxxxxx> writes:
> > I'm just curious, would this always work?:
> >
> > modprobe raw
> > raw /dev/raw/raw1 /dev/xyz
> >
> > or should you wait for /dev/raw/rawctl after modprobe (udevadm settle or
> > sleep)?
This is generic problem and I don't think for utils like raw(8) is
there any elegant way how to wait for rawctl node.
IMHO the right solution is write robust scripts and expect "bad things"
from your OS :-)
> Interesting -- the modprobe manual page doesn't state explicitly whether
> or not the module initialization actions will be completed before
> modprobe returns.
Well, module initialization may also trigger uevent and the rest is
userspace (udev) business. In this case things are completely out of
kernel+modprobe control, so "module initialization done" is irrelevant
information.
Karel
--
Karel Zak <kzak@xxxxxxxxxx>
http://karelzak.blogspot.com
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
