jjfeiler@nntp-server.caltech.edu (John Jay Feiler) (03/12/91)
Does anyone know if there is a version of tcsh for the next that will allow remote logins. Our sysadmins here claim that the version of tcsh that we have here (I think it's 5.12 ?) is the reason that I can't rlogin to one of our nexts from a sun. If there's no tcsh, does anyone know if bash will work on the NeXT? John Feiler
barry@pico.math.ucla.edu (Barry Merriman) (03/13/91)
In article <1991Mar12.072203.12123@nntp-server.caltech.edu> jjfeiler@nntp-server.caltech.edu (John Jay Feiler) writes: > >If there's no tcsh, does anyone know if bash will work on the NeXT? > as pointed out, the nexts own csh is really a CMU-shell that supports almost all tcsh amenities. just put: set editmode=emacs in your .cshrc and put bind-to-key FilenameExpansion "\^I" in a file called .bindings (used to store your personal key-bindings for the CMU-shell; do man csh on a next for more info and the full list of bindings---they have most emacs functions) and away you go! I don't use tcsh anymore at all. -- Barry Merriman UCLA Dept. of Math UCLA Inst. for Fusion and Plasma Research barry@math.ucla.edu (Internet)
melling@cs.psu.edu (Michael D Mellinger) (03/13/91)
In article <1991Mar12.072203.12123@nntp-server.caltech.edu> jjfeiler@nntp-server.caltech.edu (John Jay Feiler) writes:
Does anyone know if there is a version of tcsh for the next that will allow
remote logins. Our sysadmins here claim that the version of tcsh that we
have here (I think it's 5.12 ?) is the reason that I can't rlogin to one of our
nexts from a sun.
If there's no tcsh, does anyone know if bash will work on the NeXT?
You need to add tcsh (full path) to your /etc/shells file.
-Mikemelling@cs.psu.edu (Michael D Mellinger) (03/13/91)
Oh, rlogin. Different story. I was thinking of ftp. Is tcsh still available from the archive sites? It seems to work under 2.0, with the notable exception of TAB for file name expansion(exec'ing tcsh will fix this -- .i.e rerun it) Have the legalities of posting tcsh ever been worked out? -Mike
paul@zaphod.uchicago.edu (Paul Burchard) (03/14/91)
In article <1991Mar12.162045.10918@math.ucla.edu> barry@pico.math.ucla.edu (Barry Merriman) writes: >In article <1991Mar12.072203.12123@nntp-server.caltech.edu> jjfeiler@nntp-server.caltech.edu (John Jay Feiler) writes: >> >>If there's no tcsh, does anyone know if bash will work on the NeXT? >> >as pointed out, the nexts own csh is really a CMU-shell that supports >almost all tcsh amenities. > One of the tcsh features NeXT-csh doesn't support is a rich prompt---one of my favorites. For example, I put the current directory (as well as my current host) into my prompt, which really helps when I'm jumping around directories and machines. (A command-line emulation of the Browser, if you like. :-) ----------------------------------------------------------------------------- Paul Burchard <burchard@math.utah.edu> ``I'm still trying to learn how to count backwards from infinity...'' -----------------------------------------------------------------------------
cattelan@mermaid.micro.umn.edu (Russell Cattelan) (03/14/91)
jjfeiler@nntp-server.caltech.edu (John Jay Feiler) writes: >Does anyone know if there is a version of tcsh for the next that will allow >remote logins. Our sysadmins here claim that the version of tcsh that we >have here (I think it's 5.12 ?) is the reason that I can't rlogin to one of our >nexts from a sun. >If there's no tcsh, does anyone know if bash will work on the NeXT? I put the binary for tcsh-5.20.02 (the latest version) on cs.orst.edu a couple of months ago. But I would suspect your problem is with /usr/etc/rlogind (or was that rpc.rlogind Whatever) and /bin/login. For some reason unless the name of your shell is /bin/csh the remote logins just hang. I tried many different things includeing cp /bin/csh /usr/local/bin/tcsh and the logins would still failed. I also tried cp /usr/local/bin/tcsh /bin/csh and it worked (ie I was running tcsh but called /bin/csh) So what I finally did was replace /bin/login and /usr/etc/rlogind with the old 1.0 versions (Yes! it only worked when I replaced both). Logins are still slow 20-30 sec or more but they do work. BTW I know Nexts csh has some of the command line stuff that tcsh has but if one is a serious tcsh user: csh is still really lame. Alos the diffs for tcsh now come patchable(?) for the reno csh sources and the tahoe csh source. They can be gotten from tesla.cornell.edu -Russell Cattelan -> Oh Sh*t here comes thet wall again<-
davis@en.ecn.purdue.edu (E Robert Davis) (03/14/91)
In article <1991Mar14.051506.1851@midway.uchicago.edu> paul@zaphod.uchicago.edu (Paul Burchard) writes: > >One of the tcsh features NeXT-csh doesn't support is a rich >prompt---one of my favorites. For example, I put the current >directory (as well as my current host) into my prompt, which really helps >when I'm jumping around directories and machines. (A command-line >emulation of the Browser, if you like. :-) > Actually, you can do this with csh. Just put something like this in you .cshrc: alias cd 'chdir \!* ; set prompt="[$cwd] "' cd ## note: this sets initial prompt to $HOME You could stick your host in there ($host) or the current command (for reference with the history command) etc. >----------------------------------------------------------------------------- >Paul Burchard <burchard@math.utah.edu> >``I'm still trying to learn how to count backwards from infinity...'' >----------------------------------------------------------------------------- Robert
hardy@golem.ps.uci.edu (Meinhard E. Mayer (Hardy)) (03/14/91)
The prompt can be fixed: here are the appropriate lines in .cshrc
# make the prompt palatable
if( ${?prompt} ) then
set host=`hostname`
set prompt='`whoami`@`hostname`%${cwd}\[!\]\ '
### chdir and prompts
alias cd chdir \!:\* \; \
set prompt='`whoami`@`hostname`%${cwd}\[!\]\ ' \; \
setenv CWD '$cwd'
alias pd pushd \!:\* \; \
set prompt='`whoami`@`hostname`%${cwd}\[!\]\ ' \; \
setenv CWD '$cwd'
alias pp popd \!:\* \; \
set prompt='`whoami`@`hostname`%${cwd}\[!\]\ ' \; \
setenv CWD '$cwd'
cd .
set editmode=emacs
------
This is not quite as good as a tcsh prompt, but, unless you are in
hardy@weyl%/NextLibrary/TeX/tex/formats[60]
it is reasonable.
What i am really missing in the NeXT csh is the spell-checking
tcsh has (on my good old HP-Bobcat). Here is an example:
-----
hardy@golem{users/hardy}[52>more .csherc
CORRECT>more .cshrc (y/n)? no
.csherc: No such file or directory
hardy@golem{users/hardy}[53>
-----
To say nothing of the "at" facility, and other goodies,
so sooner or later I am going to get tcsh.
Hardy
-------****-------
Meinhard E. Mayer (Prof.) Department of Physics, University of California
Irvine CA 92717;(714) 856 5543; hardy@golem.ps.uci.edu or MMAYER@UCI.BITNEThardy@golem.ps.uci.edu (Meinhard E. Mayer (Hardy)) (03/14/91)
One simple way around this (my X in HP-UX 7.0 doesn't like /bin/tcsh either)is to log in with csh and then start up tcsh from .login. Disadvantage: two-step logout. Hardy -------****------- Meinhard E. Mayer (Prof.) Department of Physics, University of California Irvine CA 92717;(714) 856 5543; hardy@golem.ps.uci.edu or MMAYER@UCI.BITNET
louie@sayshell.umd.edu (Louis A. Mamakos) (03/14/91)
In article <HARDY.91Mar14000630@golem.ps.uci.edu> hardy@golem.ps.uci.edu (Meinhard E. Mayer (Hardy)) writes: >One simple way around this (my X in HP-UX 7.0 doesn't like >/bin/tcsh either)is to log in with csh and then start up >tcsh from .login. >Disadvantage: two-step logout. Alternatively, you can "exec tcsh" in your .login and not have the double logout. What you really want to do is to look at /etc/shells, and perhaps add your favorite shell to the list there. louie
matthews@lewhoosh.umd.edu (Mike Matthews) (03/14/91)
To put the current directory into your prompt, you don't need tcsh. Just: alias cd 'cd \!*; set prompt="$host `pwd` > ' The `pwd` part is the important one here. Now, true, this gets confused with pushd and popd, but you can alias them too (well, popd might prove a wee bit difficult -- perhaps alias popd 'popd ; cd .' would do the trick). tcsh is nice, yes, but NeXT's csh isn't as braindead as most people think. [btw, those aliases work on any csh as far as I know] ------ Mike Matthews, matthews@lewhoosh.umd.edu (NeXT)/matthews@umdd (bitnet) ------ I see the eigenvalue in thine eye, I hear the tender tensor in thy sigh. Bernoulli would have been content to die Had he but known such a-squared cos 2(thi)!
chet@odin.INS.CWRU.Edu (Chet Ramey) (03/16/91)
In article <1991Mar14.054625.3751@cs.umn.edu> cattelan@mermaid.micro.umn.edu (Russell Cattelan) writes: >>If there's no tcsh, does anyone know if bash will work on the NeXT? Yes, it will. >But I would suspect your problem is with /usr/etc/rlogind (or was that >rpc.rlogind Whatever) and /bin/login. For some reason unless the name >of your shell is /bin/csh the remote logins just hang. When I brought CWRU bash 1.07 up on a NeXTstation, I ran into this, and found out that there are a number of bugs in /usr/etc/rlogind. Here's an excerpt from mail I sent to someone explaining it. Now that you're working on bash for NeXT, let me ask you if you've run into this bug under 2.0: bash, as a login shell, hangs on rlogin into the NeXT. But it works fine on telnet. On rlogin, I even get no output to stdout from the 'tset' (or debugging 'echo's) in my startup files. It's getting stuck in initialize_jobs (). There is a bug in the NeXT /usr/etc/rlogind that causes bash to be started with the terminal still belonging to the rlogind process, and its process group set to 0 (so that getpgrp() returns 0). It looks like there's a stray setpgrp(0, 0) in the rlogind code that NeXT is not handling like 4.3 BSD. >I tried many different things includeing cp /bin/csh /usr/local/bin/tcsh >and the logins would still failed. >I also tried cp /usr/local/bin/tcsh /bin/csh and it worked >(ie I was running tcsh but called /bin/csh) This is probably an /etc/shells issue. Chet -- Chet Ramey ``Now, somehow we've brought our sins Network Services Group back physically -- and they're Case Western Reserve University pissed.'' chet@ins.CWRU.Edu My opinions are just those, and mine alone.
ddh@ombrage.mi.org (Dave Hale) (03/17/91)
In article <1991Mar14.123200.6143@ni.umd.edu> louie@sayshell.umd.edu (Louis A. Mamakos) writes: >In article <HARDY.91Mar14000630@golem.ps.uci.edu> hardy@golem.ps.uci.edu (Meinhard E. Mayer (Hardy)) writes: >>One simple way around this (my X in HP-UX 7.0 doesn't like >>/bin/tcsh either)is to log in with csh and then start up >>tcsh from .login. >>Disadvantage: two-step logout. > >Alternatively, you can "exec tcsh" in your .login and not have the double >logout. > >What you really want to do is to look at /etc/shells, and perhaps add I have a show little C-program that will allow you to change your login shell to whatever you like and have the shell act just like it was the login shell. Basically all you have to do is have a program that does an exec on the shell with arg[0] as -shellname. (i.e. -tcsh) It's an easy program to write, but if there is enough interest I can post it to the net (5-10 lines). - Dave -- Dave Hale ddh@orage.mi.org - Can alse accept NeXT mail at this address. ddh@ombrage.mi.org - Regular mail only, please.