Re: tty1 should start after boot and default bundles are finished.
Reply #2 –
Enabling cryptboot-s6 results in the following tty1 mess.
Artix Linux 5.9.10-artix1-1 (tty1)
artixlinux login: Unlocking cryptboot
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
_(cursor)
Seeing this on every boot boggles my mind. Typing my user name over this message makes me feel ill. It decreased quality of my life.
It is not a login prompt. It is a mess. It killed the magical elegance.
I also discovered that redirecting /dev/console to tty8 prevents me from seeing LUKS passphrase prompt on tty1.
If console is on tty8, LUKS passphrase prompt appears on tty8.
I thought it took forever for LUKS to unlock, but LUKS passphrase prompt was on tty8.
I also don't like the fact that s6-linux-init takes care of tty1 instead of letting it run as an init service. Runit delegates all ttys and consoles to init services.
S6 is almost perfect although dependencies are a file instead of a directory. Anopa turned dependencies into a directory. Directory is easier to manage for package managers. A package can have a file in a directory. If a dependency is an empty regular file in a directory, I can add my own dependencies without interfering with package managers. If I wrote s6 init system, I would let an init service define the following directories: depend, depended, want, wanted, after, and before.
Allowing init services to define their own reverse dependencies can prevent init services from modifying each other. I don't like the fact that cryptboot-s6 modifies /etc/s6/sv/mount-filesystems/dependencies.