In article <vi0vprg03jg60@corp.supernews.com>,
Gene Tolli <geetee@charter.net> wrote:
>I recently upgraded from OS9.2.2 to Jaguar, and so far I've been very
>pleased with the new OS. I've been using the Sams TYS OSX book to help
>with the transition.
>
>Tonight I was working through Chapter 23: Security Considerations. The
>authors recommend disabling shell access for non-admin accounts using
>the following scheme:
>
>1. Open a Terminal window.
>2. Type cd /bin [return]
>3. Type sudo chmod o-x *sh [return]
>4. Close the Terminal window.
>
>I was logged in as admin, and typed "logout" before quitting Terminal.
>
>My problem: now I don't seem able to access the command line from *any*
>account, even as admin. The Terminal window has the heading "Command
>Completed", and contains the message:
>
>[Process exited - exit code 101]
>
>I can't type anything, all I get is an error chime.
>
>Could anyone explain what I've done, and - if possible - how I might
>undo it?
>
>Thanks in advance.
You've made it so only user 'root' or a member of of the group 'wheel'
can execute a shell. No shell means no login. I don't know why you'd
want to do such a thing when the Sharing control panel lets you turn off
remote logins.

Reboot while holding down Option-S. Type:

cd /bin
chmod o+x *sh
logout

That will undo what you did. Repairing permissions with Disk Utility
might do the trick too.