22 Oct
2019
22 Oct
'19
1:36 p.m.
From: Sean Dwyer
chdir seems to be a syscall in 7 (sys4.c)
It's been a system call forever, see e.g.:
https://minnie.tuhs.org//cgi-bin/utree.pl?file=V1/man/man2/chdir.2
(And the working dir was a property of the process, not data in the shell.)
Noel
22 Oct
22 Oct
2:22 p.m.
New subject: What was your "Aha, Unix!" moment?
On a somewhat related note, if someone could shine some light on, if such
chdir() which wasn't yet integrated into the shell function independent of
fork() as in did fork() just spawn off a new child shell if one did chdir()
or more generally how did processes interact when/if more than one child
existed. I know PDP-7 had some archaic IPC but haven't gotten around to
grokking fork.s or others to understand the actual operation.
On Tue, 22 Oct 2019 at 7:06 PM, Noel Chiappa <jnc(a)mercury.lcs.mit.edu>
wrote:
--
Abhinav Rajagopalan
From: Sean
Dwyer
chdir seems to be a syscall in 7 (sys4.c)
It's been a system call forever, see e.g.:
https://minnie.tuhs.org//cgi-bin/utree.pl?file=V1/man/man2/chdir.2
(And the working dir was a property of the process, not data in the shell.)
Noel
8:08 p.m.
New subject: What was your "Aha, Unix!" moment?
On Tue, Oct 22, 2019 at 07:52:32PM +0530, Abhinav Rajagopalan wrote:
On a somewhat related note, if someone could shine
some light on, if
such chdir() which wasn't yet integrated into the shell function
independent of fork() as in did fork() just spawn off a new child shell
if one did chdir() or more generally how did processes interact when/if
more than one child existed. I know PDP-7 had some archaic IPC but
haven't gotten around to grokking fork.s or others to understand the
actual operation.
The best place to learn all this is Dennis' paper on the Evolution of Unix:
http://www.read.seas.harvard.edu/~kohler/class/aosref/ritchie84evolution.pdf
Cheers, Warren
1654
days inactive
1654
days old
2 comments
3 participants
participants (3)
-
Abhinav Rajagopalan -
jnc＠mercury.lcs.mit.edu -
Warren Toomey