Ubuntu servers should display information during boot by default
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Release Notes for Ubuntu |
Fix Released
|
Undecided
|
Unassigned | ||
Ubuntu CD Images |
Fix Released
|
High
|
Colin Watson | ||
grub-installer (Ubuntu) |
Fix Released
|
High
|
Colin Watson | ||
Lucid |
Fix Released
|
High
|
Colin Watson | ||
ubuntu-meta (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Lucid |
Invalid
|
Undecided
|
Unassigned | ||
upstart (Ubuntu) |
Fix Released
|
High
|
Scott James Remnant (Canonical) | ||
Lucid |
Fix Released
|
High
|
Scott James Remnant (Canonical) |
Bug Description
As of Lucid, the work done for a sleek boot for Desktop also affected Server. On beta1, the server boots without any message, displays a graphical splash screen, and exits to the login prompt.
Server users expect to have a verbose boot by default. In particular, they want to get the output of the init.d scripts (complete with "[OK]") to track what happens (like on previous releases). They don't really care about a graphical splash screen.
I understand this won't result in silent upstart scripts to suddenly become self-aware and describe what they are doing, but at least that would allow the legacy init.d scripts to appear as they always did.
Related bug: bug 542666 (init.d output suppressed even when splash and quiet have been removed from boot options)
Changed in ubuntu-meta (Ubuntu): | |
assignee: | nobody → Colin Watson (cjwatson) |
description: | updated |
Changed in ubuntu-meta (Ubuntu): | |
importance: | Undecided → High |
milestone: | none → ubuntu-10.04-beta-2 |
status: | New → Confirmed |
Changed in upstart (Ubuntu Lucid): | |
assignee: | Colin Watson (cjwatson) → Scott James Remnant (scott) |
Changed in grub-installer (Ubuntu Lucid): | |
status: | Triaged → Fix Committed |
Changed in grub-installer (Ubuntu Lucid): | |
status: | Fix Released → In Progress |
Changed in ubuntu-cdimage: | |
status: | Fix Released → Triaged |
tags: | added: iso-testing |
I am willing to test on a variety of hardware/VM platforms any changes made. We have a good system in place where we can rapidly update an install image and throw it on a host to see how it performs.