Package: runit Version: 2.1.2-3 Severity: normal Dear Maintainer,
* What led up to the situation? I was experimenting as per http://smarden.org/runit/replaceinit.html . * What exactly did you do (or not do) that was effective (or ineffective)? Firstly in stage 3 the login failed. I found that if I commented out the line: ! type fgetty >/dev/null 2>&1 || exec chpst -P fgetty tty5 then I can login. However then I get errors such as "No job control" and "inappropriate ioctl for device". I don't get these errors under ksh. However trying to do "sudo" under ksh does not work as it reports there is no "tty". finally it would be nice if the documents were registered with doc-base. * What was the outcome of this action? * What outcome did you expect instead? -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages runit depends on: ii libc6 2.19-22 Versions of packages runit recommends: ii fgetty 0.6-5 Versions of packages runit suggests: pn socklog-run <none> -- Configuration Files: /etc/sv/getty-5/run changed: exec getty 38400 tty5 linux -- no debconf information
