Hi, udev.service doesn't include 'settle' action, it is simplely because udev starting/adding spends some time.
Many services depends on udev directly or indirectly, so the boot process is serialized when udev starting. Currently, systemd is deeply integrated with udev, it was not easy to "First do coldplug stage which is not using udev, and then do hotplug later through udev". 2011/5/18 microcai <micro...@fedoraproject.org> > > OK, here is my problem: > > > udev and systemd are from systemd overlay. > > udev is udev-168-r1 > systemd is systemd-26 > > All compiled with CFLAGS="-Os -march=native" > > systemd-analyze plot have problem generationg SVG file, so I change the > code to make a PDF. > > > Will anyone please lookat my boot analyze PDF? > > Why udev took so long to settle down ?! > > Thanks. > > _______________________________________________ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- Regards, - cee1 _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
