From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI, PLING_QUERY,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from minnie.tuhs.org (minnie.tuhs.org [45.79.103.53]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id 51b38e55 for ; Tue, 22 Oct 2019 14:23:07 +0000 (UTC) Received: by minnie.tuhs.org (Postfix, from userid 112) id 17D479BA1A; Wed, 23 Oct 2019 00:23:06 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 1F16693D91; Wed, 23 Oct 2019 00:22:48 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="fhY8toQA"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 9C92B93D91; Wed, 23 Oct 2019 00:22:46 +1000 (AEST) Received: from mail-ed1-f49.google.com (mail-ed1-f49.google.com [209.85.208.49]) by minnie.tuhs.org (Postfix) with ESMTPS id 0D74F93D8C for ; Wed, 23 Oct 2019 00:22:46 +1000 (AEST) Received: by mail-ed1-f49.google.com with SMTP id y7so5510207edo.12 for ; Tue, 22 Oct 2019 07:22:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=E4P/ah1SUFOmcdr1N3c2KWzy5+nV7QA7m7I9wLf7L4U=; b=fhY8toQA8uWGDNli1LUK3JX26iZrGi1jjcZSf610KCf/fu4WdyMJGVfXGW14CI2o4V 8qcv/N5jrGnuFWRfz9kl0EpmcPa52YCXvBtU5SCrqrnths4U5oq6/6Ej18PRDv9mjXYc hRsCzzOZcMlJE7YmnRdCE+Emsn1yzQ8E+cQCLBgPa8PT4jx8wpfIyjtWHXSFeEsdACKq or7gxRsa4PxQqtaY7QsPOeC2oVhWj6zNTblp9ntJnZcQN1xlhjBGXPNT6A3JMjle8HFv 5tLnjapkdf1B7QObSatocBpSpDXqrI0+qPnzHrCBM2sxGNFBmeyVQHi8hcvGyyh5TKA9 R2qQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=E4P/ah1SUFOmcdr1N3c2KWzy5+nV7QA7m7I9wLf7L4U=; b=n2TBnX7GO7B/tXW6c6mvSHEz2Vbe5MKU+lEeSJbnVOG98YUNC5HOs9L5MfZh2Y2cw3 GCQDujmH70HX6unTWbllU1BdOBSDHbtB0oMohOc75sQm+lq6yVx4AVwqQJjQxCrfS/LI LkJn+VvHy/oiZWDw0YDo5znznnVvxMz+SBU5l2kCdHIn/w99NX06KGhmV9MOrjH4Qs4h q7IaJTSgoG41H8nSq1kEkVch7Vu33SiIPgYH3jjhfzC/Kc8kU00718TbIHCLsCBWf7E/ XsXlhDFzZ7HcGwsDkxLRP3mEtp7vD/WZciKVIqpD1gb3vZpMp4zM3bTl9U72SGbxJT9I i/BA== X-Gm-Message-State: APjAAAUFj8U9Uc2OuDJIRyZ0ic8vLkFe/AVpXqv1ne3CRPJx9PVGzXAS e3tGe/0yuhRDHdhbDAOawMPiJ95ZvG72uDXqEKpctbAE X-Google-Smtp-Source: APXvYqzK7YaRpHqzBmErBYYF8NRwy96qXE79Ke5Uprx5s5Hqt2TFcVo4K+pskY32+VavAHhbB3YvXjzAGZG8kUdrnRQ= X-Received: by 2002:a17:906:6451:: with SMTP id l17mr27583017ejn.114.1571754164561; Tue, 22 Oct 2019 07:22:44 -0700 (PDT) MIME-Version: 1.0 References: <20191022133613.D6E8C18C0B7@mercury.lcs.mit.edu> In-Reply-To: <20191022133613.D6E8C18C0B7@mercury.lcs.mit.edu> From: Abhinav Rajagopalan Date: Tue, 22 Oct 2019 19:52:32 +0530 Message-ID: To: Noel Chiappa Content-Type: multipart/alternative; boundary="000000000000a72b2c0595808883" Subject: Re: [TUHS] What was your "Aha, Unix!" moment? X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: tuhs@minnie.tuhs.org Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --000000000000a72b2c0595808883 Content-Type: text/plain; charset="UTF-8" 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 wrote: > > 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 > -- Abhinav Rajagopalan --000000000000a72b2c0595808883 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On a somewhat related note, if someone could sh= ine 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 interac= t when/if more than one child existed. I know PDP-7 had some archaic IPC bu= t haven't gotten around to grokking fork.s or others to understand the = actual operation.=C2=A0

<= div dir=3D"auto">

On Tue, 22 Oct 2019 at 7:06 PM, Noel Chiappa <= jnc@mercury.lc= s.mit.edu> wrote:
=C2=A0 = =C2=A0 > From: Sean Dwyer

=C2=A0 =C2=A0 > chdir seems to be a syscall in 7 (sys4.c)

It's been a system call forever, see e.g.:

=C2=A0 https://minnie.tuhs.org//= cgi-bin/utree.pl?file=3DV1/man/man2/chdir.2

(And the working dir was a property of the process, not data in the shell.)=

=C2=A0 =C2=A0 =C2=A0Noel
--

Abhinav Rajagopalan

=

--000000000000a72b2c0595808883--