[systemd-devel] [PATCH] console-getty.service: conflict with vconsole-setup

Ramkumar Ramachandra artagnon at gmail.com
Tue Jul 16 07:49:51 PDT 2013

Lennart Poettering wrote:
> Similar story here. systemd-vconsole-setup is actually conditionalized
> on ConditionPathExists=/dev/tty0, i.e. will only run on systems where
> the VT is actually built into the kernel, and skipped on all others. If
> UML has not useful VT I'd recommend compiling it out of the kernel.

A couple of questions:

1. Doesn't /dev/tty0 correspond to the "current" terminal, whether
it's a virtual console or /dev/console?  Or should /dev/tty0 only ever
correspond to a virtual console, and is um Linux doing it wrong?
Should this condition be changed to /dev/tty1?

2. What if I created /dev/tty0 using mknod?

I found this in Documentation/devices.txt, although I'm not sure what
fb devices have to do with virtual consoles (there is no /dev/fb0 in
um Linux though):

  /dev/tty0 is the device that should be used to access the system video
  card on those architectures for which the frame buffer devices
  (/dev/fb*) are not applicable. Do not use /dev/console
  for this purpose.

More information about the systemd-devel mailing list