From 106516d12daeb81b1c4b106a1b1d480403c9ca19 Mon Sep 17 00:00:00 2001 From: Joachim Wiberg Date: Sun, 18 Apr 2021 11:20:36 +0200 Subject: [PATCH] doc: update tty config, detail and @console vs console Signed-off-by: Joachim Wiberg --- doc/config.md | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/doc/config.md b/doc/config.md index a1341cbb..440cf4f3 100644 --- a/doc/config.md +++ b/doc/config.md @@ -440,8 +440,8 @@ size limit is reached. ### TTYs and Consoles -**Syntax:** `tty [LVLS] [BAUD] [noclear] [nowait] [nologin] [TERM]` - `tty [LVLS] [noclear] [nowait]` +**Syntax:** `tty [LVLS] DEV [BAUD] [noclear] [nowait] [nologin] [TERM]` + `tty [LVLS] CMD [noclear] [nowait]` The first variant of this option uses the built-in getty on the given TTY device DEV, in the given runlevels. The DEV may be the special @@ -449,6 +449,11 @@ keyword `@console`, or `console`, useful on embedded systems. The default baud rate is 0, i.e., keep kernel default. +> The `tty` stanza inherits runlevel, condition (and other feature) +> parsing from the `service` stanza. So TTYs can run in one or many +> runlevels and depend on any condition supported by Finit. This is +> useful e.g. to depend on `` before starting a TTY. + **Example:** tty [12345] /dev/ttyAMA0 115200 noclear vt220 @@ -486,6 +491,10 @@ uses `ttyS0`, `ttyAMA0`, `ttyMXC0`, or anything else. Finit figures it out by querying sysfs: `/sys/class/tty/console/active`. The speed can be omitted to keep the kernel default. +> Most systems get by fine by just using `console`, which will evaluate +> to `/dev/console`. If you have to use `@console` to get any output, +> you may have some issue with your kernel config. + **Example:** tty [12345] @console noclear vt220