This bug was fixed in the package friendly-recovery - 0.2.31
---
friendly-recovery (0.2.31) wily; urgency=medium
* debian/friendly-recovery.service: Don't put this between
systemd-udev-settle.service and systemd-fsck-root.service, to avoid
blocking fsck'ing the root partitio
** Branch linked: lp:~ubuntu-core-dev/friendly-recovery/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1459475
Title:
friendly-recovery slows down boot time
To manage notifications about this
** Changed in: friendly-recovery (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1459475
Title:
friendly-recovery slows down boot time
To manage n
Phillip Susi [2015-05-28 12:48 -]:
> While we're at it, do you have any idea how to trace why it takes 6
> seconds for udev to settle?
That's mostly "don't shoot the messenger". Usually it's kernel drivers
taking long to initialize (check dmesg for what comes online at what
point); occasionall
While we're at it, do you have any idea how to trace why it takes 6
seconds for udev to settle? That seems like a long time to be fiddling
around running hotplug scripts.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Well spotted. I think we can just drop the After=systemd-udev-
settle.service. I need to think about whether we actually need it (the
upstart job called udev settle), but if so, we could just call that in
ExecStartPre= instead of Before=.
** No longer affects: systemd (Ubuntu)
** Changed in: frie
** Tags added: systemd-boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1459475
Title:
friendly-recovery slows down boot time
To manage notifications about this bug go to:
https://bugs.launchpad.
