Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!mtune!jhc
From: jhc@mtune.ATT.COM (Jonathan Clark)
Newsgroups: comp.unix.wizards
Subject: symbolic links  and csh execution
Message-ID: <1097@mtune.ATT.COM>
Date: Sat, 20-Jun-87 23:55:50 EDT
Article-I.D.: mtune.1097
Posted: Sat Jun 20 23:55:50 1987
Date-Received: Mon, 22-Jun-87 05:57:59 EDT
References: a7879@brl-adm.ARPA> <2211@bunker.UUCP>
Reply-To: jhc@mtune.UUCP (Jonathan Clark)
Organization: AT&T ISL Middletown NJ USA
Lines: 18

Keywords:


Listen guys, if I say 'cd a/b/c/d/e;cd ..' then I am now in a/b/c/d,
regardless of how many symlinks or networked file systems I had to go
through to get there. Anything else is brain-damaged.

On a similar note, for the people who are expounding starting one's
shell scripts with "#! /bin/csh", the logical continuation of this is
to start one's C programs with "#! /bin/cc", and so on. Writing a
language processor which is a partial superset of an existing standard
is one thing, and quite OK in my book; hacking the kernel to support this
automagically is quite another. Perhaps csh should have been made to
interpret a strict superset of the Bourne shell, so that normal scripts
work under it, and then csh scripts should have been interpreted via
"csh script"? Then we wouldn't have this problem.
-- 
Jonathan Clark
[NAC,attmail]!mtune!jhc

An Englishman never enjoys himself except for some noble purpose.