Interesting... Too bad ionice is in /usr/bin which automatically
qualifies it as unusable... (/usr may not be mounted yet)
--
Readahead should start in the background
https://bugs.launchpad.net/bugs/70858
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Attachment added: "bootchart with backgrounded and ioniced readahead"
http://launchpadlibrarian.net/20598168/bootchart%2Bbackground%2Bionice.png
--
Readahead should start in the background
https://bugs.launchpad.net/bugs/70858
You received this bug notification because you are a member of
** Attachment added: "bootchart with backgrounded readahead"
http://launchpadlibrarian.net/20598155/bootchart%2Bbackground.png
--
Readahead should start in the background
https://bugs.launchpad.net/bugs/70858
You received this bug notification because you are a member of Ubuntu
Bugs, which is
attached are some bootcharts for
released version of readahead (27 seconds)
+ background (22 seconds / 19 % faster)
+ ionice -c3 (21 seconds / another 3 % faster)
** Attachment added: "bootchart with released version of readahead"
http://launchpadlibrarian.net/20598140/
Rationale was provided for the change to foreground.
Please provide equal or more research
** Changed in: readahead-list (Ubuntu)
Status: Unconfirmed => Rejected
--
Readahead should start in the background
https://launchpad.net/bugs/70858
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
Hmm, seems the contrary of:
https://launchpad.net/distros/ubuntu/+source/readahead-list/+bug/59716
However, booting with readahead in the foreground (thus stalling the
bootprocess), my bootime in edgy is roughly 55 seconds, while it is 47
seconds when readahead is started in the background...
And
