StreamlinedBoot

Revision 12 as of 2006-02-08 03:21:55

Clear message

Summary

Identify what we're actually doing during boot up, and decide what we actually need to be doing and drop (or move) anything we don't; regroup the boot sequence into clear targets ("hardware detection", "console setup", "filesystem checking and mounting", etc.).

Rationale

Use cases

Scope

Design

A good idea would be to do this like the KDE and Gnome splash screens. But instead of using icons, we'd use flashing text on Usplash and the progress bar to show the boot progress.

attachment:streamlinesplash.gif

The percieved time-to-boot is the time from pushing the power button till the user can interact with the system for his/her most common needs. Can we reorder the boot targets to shorten the percieved time-to-boot? Consider starting programs like hplip, cupsys, makedev, sshd, powernowd, rsync, openafs, cron, anacron, atd, binfmt-support, alsa, apmd, bluez-utils, fetchmail and acpi-support after the login screen (graphical or not) has been displayed and even suspending their startup until after the user has logged in and the basic encironment (terminal or desktop) is set up. -PhilipGanchev

Implementation

The best idea would be to make Usplash only draw those multiple strings, but then code in a system that still works with our output system for the current Usplash, making Usplash flash different text based off coded triggers in the Usplash code.

Code

Data preservation and migration

Outstanding issues

Bug comparing Breezy to Mandriva's boot speed: https://launchpad.net/distros/ubuntu/+source/boot/+bug/3485

BoF agenda and discussion

viper550: Why not do this like the KDE splash screen, this might be a feasable approach to this idea.

CategorySpec