From: arnold@cc.gatech.edu (Arnold Robbins)
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: A delicious thought
Date: Tue, 18 May 1993 13:08:40 -0400 [thread overview]
Message-ID: <9305181708.AA05746@penfold.cc.gatech.edu> (raw)
In-Reply-To: Alan Watson's 52-line message on May 18, 1:01pm
Everything old is new again.....
I read in an early history of unix paper that on the very early unix
systems (pdp-7 vintage!) everything in fact worked this way. You typed
a command. The shell exec'ed it, and then the code in exit() would re-exec
the shell.
When they added fork to the system, they noticed that 'cd' didn't take them
anywhere.... At that point it became built-in to the shell.
I could almost see doing this with limit. cd is a bit expensive, methinks
(just think about the TWO call through nami. One to find cd, the next to
do the chdir. ugh)
Arnold
next reply other threads:[~1993-05-18 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-05-18 17:08 Arnold Robbins [this message]
-- strict thread matches above, loose matches on Subject: below --
1993-05-19 14:04 Alan Watson
1993-05-18 18:19 Alan Watson
1993-05-19 10:00 ` Richard Brooksby
1993-05-18 17:10 Byron Rakitzis
1993-05-18 17:01 Alan Watson
1993-05-18 19:39 ` root
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9305181708.AA05746@penfold.cc.gatech.edu \
--to=arnold@cc.gatech.edu \
--cc=rc@hawkwind.utcs.toronto.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).