close 1063905 thanks and keep it closed Vincent Lefevre dixit: >On 2024-02-14 15:22:43 +0000, Thorsten Glaser wrote: >> Vincent Lefevre dixit: >> >> >/usr/bin/mksh and /usr/bin/mksh-static are no longer in /etc/shells: >> >> That’s correct. Their presence was a bug caused by add-shells >> misbehaviour which I have worked around in maintainer scripts.
>This is not a bug in add-shell, but done on purpose as the presence >of the real path in /etc/shells is *needed* by some programs. See It *is* a bug in add-shell, it should never have followed symbolic links, because they are subject to change without notice. >> They should never have been in there. For example /bin/mksh-static is a symbolic link and points to whereever works, and users who want to use this are sup‐ posed to have that symlink as shell, never the target which can go away. > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817168 The OP’s $SHELL should not be set to /usr/bin/bash as that value is not in /etc/shells and not its canonical path in the first place. The whole *purpose* of /etc/shells is to document the shells’ canonical paths that can be used as login shells for user accounts, so therefore, the info in /etc/shells is the primary source for the paths and must be consulted, and whatever set the OP’s $SHELL to a different path was buggy. For the mksh package, exactly the canonical path /bin/mksh and, since some releases ago, /bin/mksh-static are supported as shell entries, no other paths. bye, //mirabilos -- Sometimes they [people] care too much: pretty printers [and syntax highligh- ting, d.A.] mechanically produce pretty output that accentuates irrelevant detail in the program, which is as sensible as putting all the prepositions in English text in bold font. -- Rob Pike in "Notes on Programming in C"
