9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: plan9fans@ntlworld.nospam.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Novice question - run as other
Date: Wed, 17 Mar 2004 18:29:43 +0000	[thread overview]
Message-ID: <12ee874bd1d1ca3246f99555054e2820@snellwilcox.com> (raw)

Hi,

My all-time favorite Unix story, lifted from
http://cm.bell-labs.com/cm/cs/who/dmr/hist.html

Although the multiple-process idea slipped in very easily indeed,
there were some aftereffects that weren't anticipated.  The most
memorable of these became evident soon after the new system came up
and apparently worked.  In the midst of our jubilation, it was
discovered that the chdir (change current directory) command had
stopped working.  There was much reading of code and anxious
introspection about how the addition of fork could have broken the
chdir call.  Finally the truth dawned: in the old system chdir was an
ordinary command; it adjusted the current directory of the (unique)
process attached to the terminal.  Under the new system, the chdir
command correctly changed the current directory of the process created
to execute it, but this process promptly terminated and had no effect
whatsoever on its parent shell!  It was necessary to make chdir a
special command, executed internally within the shell.  It turns out
that several command-like functions have the same property, for
example login.


-Steve


             reply	other threads:[~2004-03-17 18:29 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-17 18:29 plan9fans [this message]
     [not found] <200403170948.i2H9mi3W084127@adat.davidashen.net>
2004-03-17 18:24 ` 9nut
2004-03-18  7:38   ` boyd, rounin
  -- strict thread matches above, loose matches on Subject: below --
2004-03-17 12:43 David Presotto
2004-03-17 17:03 ` ron minnich
2004-03-17 17:13   ` rog
2004-03-17 17:13     ` David Presotto
2004-03-17 18:00   ` David Tolpin
2004-03-17 18:12     ` ron minnich
2004-03-17 18:14     ` David Presotto
2004-03-17 19:34     ` rog
2004-03-17 19:52       ` Russ Cox
2004-03-17 19:58         ` rog
2004-03-18  4:21     ` Martin C.Atkins
     [not found] <200403161953.i2GJrNMv080779@adat.davidashen.net>
2004-03-16 22:54 ` 9nut
2004-03-17  7:18   ` David Tolpin
2004-03-17  8:10     ` Geoff Collyer
2004-03-17  8:24       ` David Tolpin
2004-03-17  8:55         ` Geoff Collyer
2004-03-17  9:04           ` David Tolpin
2004-03-17  9:19           ` Bruce Ellis
2004-03-17 10:31           ` boyd, rounin
2004-03-17 14:01             ` Dave Lukes
2004-03-17  9:33     ` 9nut
2004-03-17  8:54       ` David Tolpin
2004-03-17  8:56         ` Charles Forsyth
2004-03-17  9:07           ` David Tolpin
2004-03-17  9:17             ` Charles Forsyth
2004-03-17  9:28               ` David Tolpin
2004-03-17 10:08         ` 9nut

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=12ee874bd1d1ca3246f99555054e2820@snellwilcox.com \
    --to=plan9fans@ntlworld.nospam.com \
    --cc=9fans@cse.psu.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).