Ubuntu servers should display information during boot by default

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.

This bug involves changes to a number of packages. The changes I know about are as follows:

 * plymouth: fix segfault in vga16fb renderer induced by VT activation while not actually using the renderer (this is already done in plymouth 0.8.1-3, so I shan't bother opening a bug task for it)
 * upstart: 1) add 'console output' to /etc/init/rc.conf, or make it the default for all jobs (Scott, have you decided which you want yet? I prefer the former on grounds of minimum impact); 2) add 'env INIT_VERBOSE' to /etc/init/rc.conf so that INIT_VERBOSE=yes on the kernel command line works, the way it appears to be intended to
 * ubuntu-meta: move plymouth-theme-ubuntu-logo from standard to desktop-common seed, leaving standard with only the built-in details theme, plus plymouth-theme-ubuntu-text to satisfy the Recommends field
 * grub-installer: make it possible for the server CDs to be configured such that 'splash' never ends up on the installed system's kernel command line
 * ubuntu-cdimage: configure the server CDs thus, while making sure that the alternate CDs still get 'splash'

The result of this will be that console messages, including output from init scripts, end up on tty7 during boot. After boot has finished, we'll switch to tty1, which will just have a login prompt on it, but Alt-F7 will show the init script output again. Not all init scripts will produce output, since some are guarded by VERBOSE checks; if you want to see these, boot with INIT_VERBOSE=yes. I believe the default, without VERBOSE, should show very little by default but a reasonable amount of interesting status output for any server system running a non-trivial number of daemons.

Thierry, does this sound OK to you? I'm going to get started with the straightforward bits.

Actually, disregard the ubuntu-meta part. I think we should leave plymouth-theme-ubuntu-logo installed, in the knowledge that it won't be used unless we use the 'splash' boot parameter. That way, anyone using a server installation who *does* want a splash screen just has to add 'splash' to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and run update-grub.

However, we will need to release-note this behaviour for upgraders, and possibly change update-manager to delete the 'splash' parameter on server upgrades.

Colin, that plan sounds good to me.

On Wed, 2010-03-31 at 22:02 +0000, Colin Watson wrote:

> * upstart: 1) add 'console output' to /etc/init/rc.conf, or make it
> the default for all jobs (Scott, have you decided which you want yet?
> I prefer the former on grounds of minimum impact); 2) add 'env
> INIT_VERBOSE' to /etc/init/rc.conf so that INIT_VERBOSE=yes on the
> kernel command line works, the way it appears to be intended to
>
It's going to be the former.

I suddenly realised that changing the default this late in the cycle,
and so it's different from upstream Upstart, was a plan made entirely of
crazy.

Scott
--
Scott James Remnant
<email address hidden>

This bug was fixed in the package upstart - 0.6.5-6

---------------
upstart (0.6.5-6) lucid; urgency=low

  * Merge fixes from trunk:
    - double-quoting of NIH_CFLAGS and NIH_DBUS_CFLAGS on --with-local-libnih
    - document "env KEY" behaviour
  * conf/rc.conf, conf/rc-sysinit.conf:
    - enable console output. LP: #548954.
    - pass value of INIT_VERBOSE from kernel command-line.
 -- Scott James Remnant <email address hidden> Thu, 01 Apr 2010 19:25:36 +0100

This bug was fixed in the package grub-installer - 1.49ubuntu10

---------------
grub-installer (1.49ubuntu10) lucid; urgency=low

  * Historically, Ubuntu's default behaviour in the absence of command-line
    arguments to the installer has been to pass 'splash' to the installed
    system so that it gets a splash screen (and similarly 'quiet'). There's
    some argument that this behaviour should require passing 'splash' to the
    installer as well, but it's too late in the Lucid cycle for this change.
    Nevertheless, we need a way to configure images such that they don't get
    'splash' in the installed system, so introduce a 'nosplash' argument
    which inhibits this, for use by the server CD (LP: #548954).
 -- Colin Watson <email address hidden> Thu, 01 Apr 2010 23:44:48 +0100

revno: 1542
fixes bug(s): https://launchpad.net/bugs/548954
committer: Colin Watson <email address hidden>
branch nick: debian-cd
timestamp: Fri 2010-04-02 13:33:38 +0100
message:
  add nosplash to kernel parameters on ubuntu-server (LP: #548954)

Testing with 20100406 beta2 candidate, "splash" is still present in the boot options. That makes the splash screen show, and alt-F7 switch to an empty screen.

Maybe unrelated, but at first boot after install, the splash screen was echoing lots of "could not write bytes: broken pipe" errors (this could not be reproduced on subsequent boots).

This bug was fixed in the package grub-installer - 1.49ubuntu11

---------------
grub-installer (1.49ubuntu11) lucid; urgency=low

  * 'nosplash' doesn't work because it isn't passed through by user-params.
    Use debian-installer/splash=false for this behaviour instead
    (LP: #548954).
 -- Colin Watson <email address hidden> Tue, 06 Apr 2010 13:26:16 +0100

revno: 1546
committer: Colin Watson <email address hidden>
branch nick: debian-cd
timestamp: Tue 2010-04-06 14:13:38 +0100
message:
  preseed debian-installer/splash=false on server images rather than putting nosplash on the kernel command line (LP: #548954)

Is it possible that this (very good) decision makes it impossible to see actual errors and suggestions?

For example, if you can't mount a filesystem, nothing on the screen will say so, and you don't see the suggestions. (like pressing S or M) while these keys do work.

@Alvin: I think the mountall missing prompt for S/M is the exception, not the rule. Filed bug 563916 to track that.

Documented now at <https://wiki.ubuntu.com/LucidLynx/ReleaseNotes#Changes%20in%20boot-time%20output%20on%20Ubuntu%20Server>.