# already been discovered
-/sbin/udevadm trigger --action=add
+/sbin/udevadm trigger --action=add --type=subsystems
+/sbin/udevadm trigger --action=add --type=devices
# Now wait for udevd to process the uevents we triggered
/sbin/udevadm settle
Seems
/sbin/udevadm settle
Seems logical, any reason not to?
From the manpage, --type=devices is the default, so this is a superset
of what we're triggering today. So yes, and oops. (Looks like we
should have been doing this for a while now.) :-)
signature.asc
Description: OpenPGP digital
DJ Lucas wrote:
stuff about settle being broken
I see some traffic on linux-hotplug about this as well, so it looks like
it's not LFS-specific, at least. (Arch and Debian have both had bugs
reported about this.) The messages from Kay so far seem encouraging, as
well.
...Oh, and I see the
On 05/16/2011 12:59 AM, Bryan Kadzban wrote:
DJ Lucas wrote:
stuff about settle being broken
I see some traffic on linux-hotplug about this as well, so it looks like
it's not LFS-specific, at least. (Arch and Debian have both had bugs
reported about this.) The messages from Kay so far seem
happens if you boot with init=/bin/bash, then manually run scripts
one at a time, until you get to udev, then both (a) run it, and (b) list
out /dev/sd*, in the same shell command? What happens if you do (a) and
(b), then (c) rerun udevadm settle, then list again? (All in the same
command again
On 05/11/2011 11:25 PM, Bruce Dubbs wrote:
DJ Lucas wrote:
After updating from udev-165 to udev-168, I ran into a timing issue
with settle using tmpfs for /dev. My swap partition failed to mount
because the device node was not present. No other changes than those
made to the bootscripts and
On 5/12/11 3:09 AM, DJ Lucas wrote:
Sure there is...a fully event driven init as Bryan described earlier. I
just don't find that to be transparent enough for my taste, nor udev
quite mature enough just yet (as evidenced by this very issue), though
it is getting there slowly but surely.
DJ Lucas wrote:
On 05/11/2011 11:14 PM, Bryan Kadzban wrote:
Where is your swap?
/dev/sda3...which gives a much better explanation as to why it works
with devtmpfs. I did not buy the faster bit.
Yeah, that sounds about right.
(I'm thinking the kernel isn't sending the event to udev in
After updating from udev-165 to udev-168, I ran into a timing issue with settle
using tmpfs for /dev. My swap partition failed to mount because the device node
was not present. No other changes than those made to the bootscripts and FS
layout to account for /run. I rebooted a few more times to
to swap them out for the standard scripts?
What happens if you boot with init=/bin/bash, then manually run scripts
one at a time, until you get to udev, then both (a) run it, and (b) list
out /dev/sd*, in the same shell command? What happens if you do (a) and
(b), then (c) rerun udevadm settle
DJ Lucas wrote:
After updating from udev-165 to udev-168, I ran into a timing issue
with settle using tmpfs for /dev. My swap partition failed to mount
because the device node was not present. No other changes than those
made to the bootscripts and FS layout to account for /run. I rebooted
a
11 matches
Mail list logo
