shaba/systemd-stable
1
1
Fork 0
mirror of https://github.com/systemd/systemd-stable.git synced 2025-01-18 06:03:42 +03:00
Code

docs: remove /dev/tty* confusion

Browse Source 
The text said /dev/tty* as a whole was the VT subsystem and that VT is
not supported in containers.

But that's not accurate as /dev/tty* will match /dev/tty too and that
one device node is special and is not related to VT: it always points to
the current process own controlling tty, regardless what that is.

hence, rewrite /dev/tty* as /dev/tty[0-9]*.

(cherry picked from commit 6ae5c39af1da5b0b6e49278e7a33158d49ec04a5)
This commit is contained in:
Lennart Poettering 2022-12-23 18:39:54 +01:00 committed by Luca Boccassi
parent 3856b97f8b
commit f3d620f5d2
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/CONTAINER_INTERFACE.md
View File

@ -298,9 +298,9 @@ care should be taken to avoid naming conflicts. `systemd` (and in particular
you cannot link them to each other.
4. Do not pretend that the real VTs are available in the container. The VT
subsystem consists of all the devices `/dev/tty*`, `/dev/vcs*`, `/dev/vcsa*`
plus their `sysfs` counterparts. They speak specific `ioctl()`s and
understand specific escape sequences, that other ptys don't understand.
subsystem consists of all the devices `/dev/tty[0-9]*`, `/dev/vcs*`,
`/dev/vcsa*` plus their `sysfs` counterparts. They speak specific `ioctl()`s
and understand specific escape sequences, that other ptys don't understand.
Hence, it is explicitly not OK to mount a pty to `/dev/tty1`, `/dev/tty2`,
`/dev/tty3`. This is explicitly not supported.