With my very-old Linux 1.2X, with /etc/passwd, I was able to say
With my new LINUX 2.0.32, *any* parameter behind bash is rejected if I
try to login by the message
"cannot execute/bin/bash --posix": No such file or directory
Especially, even a single space behind /bin/bash typed in by using EMACS
caused the same error message. The administration tool of S.U.S.E Linux
even did not allow me to enter a space behind the path of the login
shell (but there must be a space between the executable file and the
It does not help to put this into an executable batch file
because this is rejected if I try to login by the message
"Cannot execute /bin/bash_posix: Exec format error"
The attributes are o.k., if I log in with the bash shell without
parameters, I may execute both bash --posix or bash_posix.
My system: S.U.S.E. Linux 5.1 of Nov 1997 (Linux 2.0.32),
shadow password system shadow.rpm is version 961025-6 from the S.U.S.E.
Dont tell me about .profile or so, I need the command line parameter
--posix for use with non-VT100 terminals (else ls uses VT100 escape
sequences for the directory display) !!!! Neither the file
/etc/DIR_COLORS has no effect on that, nor the bash environment variable
Please answer to the newsgroups and to me *personally* by E-Mail, too,
in german or english language !
Any help ?
/ / / Alone on the data highway...
/ / like on an allee in Hannover-Herrenhausen
/ / / Rolf Hemmerling, Germany
/ / http://home.pages.de/~rolf.hemmerling/