Package: getty-run
Version: 2.1.2-18
Severity: wishlist
Hi,
I use runit as init extensively in linux-vserver guests which don't have
console devices and thus can't run getty.
Ideally, I wouldn't even have to install the getty-run package, but I
understand it's there to help avoid people shooting themselves in the foot
by installing runit and then not having any way to log in.
However, whenever the getty-run package is installed in a vserver, I have to
manually remove the /service/getty-tty* symlinks.
Can you please modify the postinst script so it only installs getty services
for /dev/tty* devices that are actually there?
Or can we come up with a way to help people avoid shooting themselves in the
foot while not requiring me to install getty-run in vservers? For example,
runit-init could depend on "getty-run | some-way-to-log-in-interactively",
and "some-way-to-log-in-interactively" could be provided by an empty
"runit-no-getty" package as well as an "ssh-run" package that sets up a
runit service for ssh.
András
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (350, 'unstable'), (350, 'stable'), (98, 'bionic'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Versions of packages getty-run depends on:
ii runit 2.1.2-18
ii runit-helper 2.7.3
Versions of packages getty-run recommends:
ii fgetty 0.7-3
--
Sure, drinking kills brain cells, but only the weak ones.
