On 04/12/2012 08:25 AM, Mark Hounschell wrote:
On 04/11/2012 05:12 PM, Kay Sievers wrote:
On Wed, Apr 11, 2012 at 22:44, Mark Hounschell<ma...@compro.net> wrote:
Same thing. About 20 seconds after reaching the target, the device
entries
show up.
Does that block or return immediately?
rmmod<driver>;
modprobe<driver>; time udevadm settle
Your driver creates the stuff async?
After booting up to graphical login:
rmmod dgdm
modprobe dgdm ; time udevadm settle
real 0m0.107s
user 0m0.000s
sys 0m0.000s
modprobe blocks until the process has completed.
It appears, by watching the boot screen, when using sysvinit the boot
process pauses at a certain point until this has completed. It doesn't
stop as soon as it starts, but it does pause nun the less. Using systemd
it does appear to.
Correction: Using systemd it does NOT appear to.
Thanks
Mark
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
