Comment 2 for bug 1442405

The official docs [1] say to do:

--- cut here ---
# ttyS0 - getty
#
# This service maintains a getty on ttyS0 from the point the system is
# started until it is shut down again.

start on stopped rc or RUNLEVEL=[12345]
stop on runlevel [!12345]

respawn
exec /sbin/getty -L 115200 ttyS0 vt102
--- cut here ---

I have:

--- cut here ---
# ttyS1 - getty
#
# This service maintains a getty on ttyS1 from the point the system is
# started until it is shut down again.

start on stopped rc RUNLEVEL=[2345] and (
            not-container or
            container CONTAINER=lxc or
            container CONTAINER=lxc-libvirt)

stop on runlevel [!2345]

respawn
exec /sbin/getty -8 115200 ttyS1
--- cut here ---

But this isn't a race -- IMO it really is a bug, if only a documentation bug perhaps. plymouth-stop.conf has:

start on (starting gdm
          or starting kdm
          or starting xdm
          or starting lxdm
          or starting lightdm
          or starting uxlaunch
          or starting ubiquity
          or starting oem-config
          or stopped rc RUNLEVEL=[2345]
          or starting rcS
          or starting mountall-shell)

It never runs at all on a non-graphical system. Heck, I don't even see why console=tty1 or perhaps no console arg at all works correctly if there's no graphical greeter in that list. This isn't a race -- it's just completely broken in these configurations.

IMO plymouth should stop whenever a getty starts on the tty that plymouth is in charge of.

Please reopen.