Your message dated Sun, 7 Jun 2026 22:03:44 +0530 with message-id <[email protected]> and subject line ksh: fails to add /bin/ksh to /etc/shells has caused the Debian Bug report #919070, regarding ksh: fails to add /bin/ksh to /etc/shells to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 919070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919070 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: ksh Version: 93u+20120801-3.4 Severity: normal Dear Maintainer, * What led up to the situation? I installed ksh and attempted to set the login shell to /bin/ksh * What exactly did you do (or not do) that was effective (or ineffective)? `chsh -s /bin/ksh` * What was the outcome of this action? The command failed because /bin/ksh was not present in /etc/shells * What outcome did you expect instead? As ksh is part of Debian's alternatives system for the Korn Shell, I would expect /bin/ksh to ba available as a login shell. -- System Information: Debian Release: 9.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ksh depends on: ii binfmt-support 2.1.6-2 ii libc6 2.24-11+deb9u3 ksh recommends no packages. ksh suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Control: reassign -1 ksh93u+m Hi Matthew This works in the current ksh93u+m package, but the login shell path to use is /bin/ksh93 rather than /bin/ksh. The reason is that multiple ksh implementations exist (such as mksh) making use of the alternatives system to be able to switch between them cleanly. Note that the original report filed was for the previous package before migration to ksh93u+m which supports the alternatives system. Therefore, I'm closing this. Please re-open if you have issues with "chsh -s /bin/ksh93", or if that doesn't work for you with the current version. Anuradha
--- End Message ---
