Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.


There needs to be a robust and reliable mechanism for messages to be output from the boot process to usplash, the console or whatever else is running (speech daemon?) These messages should not overwrite running gettys, etc. These messages may require progress bars or prompts of their own (fsck, cryptsetup) and may require the ability to be cancelled. As well as the standard messages, other output should be captured and logged.

Release Note

This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)

It is mandatory.


Work has been done to eliminate the terminal, especially before loading into a graphical environment. It seems like an unfinished job when Ubuntu drops down from bootsplash to check the filesystem.

Use Cases



You can have subsections that better describe specific parts of the issue.


This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

UI Changes

Should cover changes required to the UI, or specific UI that is required to implement this

Code Changes

Code changes should include an overview of what needs to change, and in some cases even the specific details.



  • data migration, if any
  • redirects from old URLs to new ones, if any
  • how users will be pointed to the new way of doing things, if necessary.

Test/Demo Plan

It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during CD testing, and to show off after release.

This need not be added or completed until the specification is nearing beta.

Outstanding Issues

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.

BoF agenda and discussion

Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.

  • message output
  • logging of messages
  • not over top of getty
  • cancelable fsck
  • per-job logging?
  • usplash hooks
  • speech hooks


use splashy or unite (like compiz and beryl did) into one: avoid wasting resources --ubuntu idea pool (forums)


BootMessages (last edited 2008-08-06 16:41:25 by localhost)