Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!spool.mu.edu!snorkelwacker.mit.edu!ai-lab!life.ai.mit.edu!rearl From: rearl@gnu.ai.mit.edu (Robert Earl) Newsgroups: comp.sys.next Subject: Bash 1.05 as login shell on NeXT Mach 2.0 Message-ID: Date: 29 Apr 91 15:42:34 GMT Sender: news@ai.mit.edu Distribution: comp Organization: (EVIL!) Lines: 22 I recently compiled and installed bash 1.05 (including some bug fixes) and then tried to make it my login shell. I tried to test it out with an rlogin from a remote host and never got a prompt; I checked the process from another terminal and it was using 95% CPU, and wasn't connected to a controlling tty! I tried telnetting there instead of rlogin, and got logged in okay, but I noticed errors from my init files such as "ioctl: operation not supported on socket", plus lots of "command not found". I inspected my environment variables, and they appeared to contain garbage, much like text that is output *by my .login*!! I removed my init files (both for bash AND csh), and rlogin still does the same thing. Telnet works okay, but from the errors my init files produced, it sounds like it's having a little trouble attaching the shell to a tty, plus a little trouble not sourcing my .login under a non-c-shell. Any ideas? --robert -- rearl@gnu.ai.mit.edu rearl@watnxt3.ucr.edu