If this isn't the right place for this bug, could please tell where the right place is.

If it is because it is not a bug at all beacause a decision has been made (after a public discussion) that ubuntu shall not log boot messages at all, and the summary "Cannot enable boot log" is actually a feature request, then could you please point to any information, that this is how ubuntu is supposed to work, and changed the status of the bug to a wishlist.

If it is because the description is wrong. That is, the way to enable logging during boot process is done differently than modifying /etc/default/bootlogd, then please let us know how you enable logging during boot.

If it is because it is assigned to the wrong ubuntu package, please reassign it to the correct ubuntu package, in staed of rejecting it as a ubuntu bug.

Please focus on the summary "Cannot enable boot log" which is a bug, even though the description of how felix.rommel tried to enable it is wrong.

The fact that bootlogd does not work with usplash is an inconvenience but not a showstopper; given the choice between no boot logging and no usplash most of us would happily accept having to turn off usplash to get boot logging (if we haven't turned it off already to see what's happening during boot).

Scott also explained that fixing the broken upstart boot logging is "is on my TODO list, but it's about item 246 right now and probably in the karmic+2 timeframe". That is a long time to go without an essential system administration diagnosis tool.

Please, maintainers, given the importance of boot logging, the probable time to fix upstart and the known effectiveness of the bootlogd workaround, please consider supporting a bootlogd package that can be installed at the same time as the upstart package, to provide boot logging until upstart is fixed.

> Please, maintainers, given the importance of boot logging, the probable
> time to fix upstart and the known effectiveness of the bootlogd
> workaround, please consider supporting a bootlogd package that can be
> installed at the same time as the upstart package, to provide boot
> logging until upstart is fixed.
>
Again, which "maintainers" are you talking to here?

You seem to be of the opinion that there's an army of developers who
work on Ubuntu's boot just idling and deliberately ignoring this bug.
There isn't. There's just me.

If you want it done more urgently, *you're going to do need to do it
yourself*

> Regards "If you want it done more urgently, *you're going to do need to
> do it yourself*", it's already done.
>
> Sergei Ivanov's workaround described in
> https://bugs.launchpad.net/upstart/+bug/98955/ from comment #29 onwards
> and in http://www.linuxquestions.org/questions/linux-general-1/howto-
> workaround-broken-upstart-boot-logging-746468/#post3637957 builds a .deb
> from source code. Sergei has said that he is not willing to maintain it
> but it's ready and tested; please consider taking it up as a supported
> ubuntu package.
>
That's not the correct way to do that; we still have the sysvinit source
package in Ubuntu (sysvinit-utils, sysv-rc and initscripts are built
from it), the correct fix would be to have that package build bootlogd
as a separate binary (or even put it in the sysvinit-utils package).

In fact, I'm pretty sure this is already "fixed in Debian" so just needs
somebody to work on a sysvinit merge.

I understand you're thinking of a standalone syslogd .deb for ubuntu only, built either from the ubuntu sysvinit source plus unspecified fixes or by merging the probably already fixed Debian source into the ubuntu sysvinit source.

I'm ignorant but willing and have a little relevant experience. If you post links to necessary technical background, procedures, sources, testing requirements etc. then I'll have a go.

If you are willing to support me in that, what is the best way for us to communicate?