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.6 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,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 499e9777 for ; Mon, 21 Oct 2019 06:23:16 +0000 (UTC) Received: by minnie.tuhs.org (Postfix, from userid 112) id 076F29B928; Mon, 21 Oct 2019 16:23:15 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id A807F93DB1; Mon, 21 Oct 2019 16:22:51 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=papnet.eu header.i=@papnet.eu header.b="Ue2zEuyP"; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=messagingengine.com header.i=@messagingengine.com header.b="Y/0F6aLc"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 0ECB793D8D; Mon, 21 Oct 2019 16:22:49 +1000 (AEST) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by minnie.tuhs.org (Postfix) with ESMTPS id 0EB6593D8C for ; Mon, 21 Oct 2019 16:22:47 +1000 (AEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 499DF21321 for ; Mon, 21 Oct 2019 02:22:46 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Mon, 21 Oct 2019 02:22:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=papnet.eu; h= date:from:to:subject:message-id:mime-version:content-type; s= fm3; bh=a7j9PwGgdaJpUpaZFRCLK1+waiFMFoLSyzfAw3mZKhw=; b=Ue2zEuyP qveZ60G6ayHkO2AufGTD5oMPATbvveyDkBHsgNzvb/+GH/5hTlWEJwoUSFBjClFA 1LTsEPQMbXvSlAX+h9arqscuZd4bmCNgQsTTTCTGqF2/X00YMJZHACG1L5rWnLXa 5Dq9UJTOvtr8T6IBvplHyc0z05uNiiOmVa8oSysCkQficibirazEXdsEAX09av18 2l8S/tdvSSnE7nP1wPQ9z/jtqfrnWYgQSOpEm2BJHPMd51MwLws4SB7XZbh7RxdA aEKRyqJX5P0ru3sbAQDg0ofk5UgtRevQixU4MqiQCRvVB1pzTReIYLUWEWnSjj1I tei45beoAAADtg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=a7j9PwGgdaJpUpaZFRCLK1+waiFMF oLSyzfAw3mZKhw=; b=Y/0F6aLcMI1acP8gLHRwifGzs3G7k2WpiX1hTJzLow+pX o4rHpznMG5b1TjbhWFdF0Fzb+JaTzseyE3fNZp7In7SWpt+HjH9xJ0zKJiZFxqzO Zp4M8CD7CtJM15C0WQ4LGtg6GEcomIJvjRW6EM4btkh8m5lzxnbjcOpXKlWuCgKn HowLcuSCFvBKJyhoqaitjUlbOJioHwOq9zxy5RnxxHaWrowCR9tKl2XAOgIwJ0Et a0bQoCg3pyJEOBp28Di5XV0gtBPXQ4aoLlyrQVx5tjOYoMGG3BQZ1Ke/CfePOkVB jNPoUf7PZhiedF0A2CuNH4qNTRHlcZQ6EJR6ZQknw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrkeeggddutdehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkgggtuggfsehttdertd dtredvnecuhfhrohhmpeetnhhgvghlohcurfgrphgvnhhhohhffhcuoegrrghpsehprghp nhgvthdrvghuqeenucfkphepjeekrdehgedrfedurddvnecurfgrrhgrmhepmhgrihhlfh hrohhmpegrrghpsehprghpnhgvthdrvghunecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from indra.papnet.eu (x4e361f02.dyn.telefonica.de [78.54.31.2]) by mail.messagingengine.com (Postfix) with ESMTPA id 9A848D6005A for ; Mon, 21 Oct 2019 02:22:45 -0400 (EDT) Date: Mon, 21 Oct 2019 08:22:42 +0200 From: Angelo Papenhoff To: tuhs@tuhs.org Message-ID: <20191021062242.GA91599@indra.papnet.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.6.0 (2016-04-01) Subject: [TUHS] PDP-7 UNIX filesystem 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: , Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" DMR explained how PDP-7 UNIX was used in "The Evolution of the Unix Time-sharing System" but having played with it myself, I stumbled in a couple of cases and found it a bit awkward to use. Maybe someone (ken and doug?) can shed some light on "elaborate set of conventions" that dmr mentioned. My questions are these: you cannot execute a program if you're in a directory you can't write into. I asked Warren about this when I first tried pdp7 unix and he explained it to me: the shell creates a link to the binary and executes it. If it can't write into the current directory, it fails to create the link and hence can't execute the program. How was this handled in practice? did users have write permissions on all directories? did you just stay in your directory all the time? . and .. Was this introduced first with PDP-11 unix or did the convention start on the PDP-7 already? It certainly seems to be the case with . but how about ..? the dd directory seems to take on the role of a sort of root directory and the now discovered program pd actually creates a file .. (haven't tried to understand what it does though yet) What does dd stand for, dotdot? directory directory? aap