Comment 46 for bug 522197

I have two concerns. One is about the ureadahead error message, which started showing up during my boot sequence only when I updated to Meerkat (Ubuntu 10.10). My second concern is the way that Ubuntu developers seem to be treating this page

I was referred here from https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/484677, because this was supposed to be the page where I will find the fix so that minor, irrelevant ureadahead error messages will not be posted to my screen before the Ubuntu splash screen shows up. I do not see the fix here. Furthermore, Scott James Remnant is quite rude and condescending on the previous page, but got he and Gabe seemed to have abandoned this page as of May 2010 without providing a step-by-step diagnostic and fix; and the problem has emerged new for me as of October 2010.

Furthermore Gabe has repeatedly given vague advice here about how other normal, non *nix-head users are supposed to go set up their own bug pages. That is less than helpful: it is dismissive. What I would recommend is: at the head of this page, whoever is entitled to edit the first posting should do the following:
1. add the following message to the first post:
"If you are experiencing boot failures after a unreadahead error message appears on your screen, the boot failure is another problem. Please go to the following page [link] to begin diagnosing the problem."
2. An experienced user of Ubuntu who has actually diagnosed boot problems should set up the new bug page. It should begin with a similar title, so that search-engine users will find it quickly as well. Then you should advise all us regular chickens about what to do next. The fact that the boot failure happens shortly after the ureadahead error-message posting should be at least a clue as to what is happening. But for people who are freaking out because they suddenly cannot boot their machine, what are you going to tell them? Probably:
A. How to boot from a CD or other partition, and then:
B. get the log files from the failing partition to look at them? Maybe:
C. refer them to postings around the Ubuntu site so that they can pursue their own diagnostic decision-trees?

At least get them started and then let them work things out through their own postings on that page. That would be helpful, rather than condescending.
Meanwhile, is there any progress in correcting upstart so that it does NOT post the following message from ureadahead?
"init: ureadahead main process (271) terminated with status 5"