Package: getty-run Version: 2.1.2-52 Severity: important X-Debbugs-Cc: Helmut Grohne <hel...@subdivi.de>, plore...@disroot.org
Hi Helmut, >From #1028181 > | Activating swapfile swap, if any...done. > | Cleaning up temporary files.... > | Cleaning up temporary files.... > | - runit: leave stage: /etc/runit/1 > | - runit: enter stage: /etc/runit/2 > | runsvchdir: default: current. > > In particular, the user has no way to log into the system as no getty > is being spawned. I see that the autopkgtest has to do this manually > via "ln -s /etc/sv/getty-ttyS0 /etc/service/". Note that the "user has no way to log into the system" is true if the only mean to login is a serial port; by default the user has 6 getty on tty[1-6] enabled. Said that I agree that it's nice to provide a setup that works out of the box; the quick fix that hopefully can improve the situation is that getty-run ship that service as enabled (it's disabled by default right now) so that the manual creation of the link is no longer needed. However I'm afraid that, since /dev/ttyS0 is hardcoded in the service, it won't work in environments where the serial device has a different name (let's say ttyS1)... > Do you think there > could be a better way to achieve this such that at least the console= > kernel command line parameter is automatically issued a getty? (just to be sure that I'm not misunderstanding the above) are you suggesting that runit grep /proc/cmdline for `console=' and if there is a match extract the device name and start a getty on that device? Or there is another more obvious way that I'm not considering? Lorenzo > > Helmut Note to myself: * the command= parameter can take several forms and there are comma separated options [1] * see also what systemd does with the getty-generator [2] [1] https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html [2] https://manpages.debian.org/testing/systemd/systemd-getty-generator.8.en.html
