In debian-user Ed wrote:
>
> No. Remember, the login process has already started, the user ('ed')
> has
>already gotten a tty, the system has printed to it (for example to tell him
>he has no mail), only when it tries to exec the default shell does the error
>occur. I can't see how tty access could cause this.
>
As always, take the error message. In 99% of case the error
message accurately reflects the problem.
The error message is "cannot execute /bin/bash".
You said you checked the permissions on /bin and on /bin/bash.
Did you also check the permissions on / ? That often happens
on newly-installed systems; it's caused by inconsiderate
decompression of inconsiderate tarfiles in /tmp. On all dynamic
libraries linked to bash and their parent directories ? While
you're at it (should not be this), also check /tmp and ~ed.
If it was somewhere else than in /bin. I'd also say to check
"noexec" mount option to the filesystem, but I think you'd have
had problems before that :-)
If this fails, try su-ing to ed, maybe that will bring up
additional data.
--
#include <std_disclaim.h> Lorens Kockum
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
