Bug#785457: cloud.debian.org: AMI don't need getty

[Emmanuel Kasper <emmanuel@libera.cc>]

Ognyan,

Can you please post a a process list of the getty processes you see in
the Amazon hvm ?

I am not aware of all the modifications made to the Debian AWS but
according to http://0pointer.de/blog/projects/serial-console.html:

Two VTs are handled specially by the auto-spawning logic: firstly tty1
gets special treatment: if we boot into graphical mode the display
manager takes possession of this VT. If we boot into multi-user (text)
mode a getty is started on it -- unconditionally, without any on-demand
logic[2].

My understanding of that applied to Xen virtualization platform that
Amazon uses, is that systemd will *always* start a getty on the default
system console,  which  for Xen will be /dev/hvc0 instead of /dev/tty1
Actually you *want* to have this one getty started, as this is where
your rescue console will be.

Now if you have more than one getty started, then there is indeed room
for improvement.

Emmanuel