On Sep 10, 2013 6:41 PM, "Jan Engelhardt" <<a href="mailto:jengelh@inai.de">jengelh@inai.de</a>> wrote: > > > On Tuesday 2013-09-10 17:41, Lennart Poettering wrote: > >On Wed, 28.08.13 13:12, Michael Marineau (<a href="mailto:michael.marineau@coreos.com">michael.marineau@coreos.com</a>) wrote: > > > >> This enables a getty on active kernel consoles even when they are not > >> the last one specified on the kernel command line and mapped to > >> /dev/console. Now the order "console=ttyS0 console=tty0" works in > >> addition to "console=tty0 console=ttyS0". > > > >The kernel already makes a distinction between the > >primary console, and all others (the latter only receive logs, but you > >cannot read from them via /dev/console iirc), and so we propagated that > >distinction into systemd, too. > > > >I can totally see that this is confusing though, as nobody remembers the > >right ordering... > > Though console= just follows the standard principle of "later values > override earlier ones", if nobody can remember the ordering, perhaps > the kernel should be taught a suboption to explicitly specify the > primary console. Think > > console.primary=ttyS0 console=tty0 > console=tty0 console.primary=ttyS0 That doesn't answer the question whether a getty should be started on secondary consoles though. My surprise was that the generator doesn't already do that, not how the primary console that gets mapped to /dev/console is chosen.