From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,HTML_MESSAGE,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 11323 invoked from network); 29 Dec 2021 20:42:44 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 29 Dec 2021 20:42:44 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 21E3C9CFE7; Thu, 30 Dec 2021 06:42:42 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id D25C99CEA9; Thu, 30 Dec 2021 06:42:16 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="EKYSt669"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id AFFE99CEA9; Thu, 30 Dec 2021 06:42:13 +1000 (AEST) Received: from mail-oi1-f177.google.com (mail-oi1-f177.google.com [209.85.167.177]) by minnie.tuhs.org (Postfix) with ESMTPS id 344829CE9F for ; Thu, 30 Dec 2021 06:42:13 +1000 (AEST) Received: by mail-oi1-f177.google.com with SMTP id x10so31812764oix.6 for ; Wed, 29 Dec 2021 12:42:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Wv5CGmCHZ3hYfSsAGHVkQECZPH23IyQz8gOrwV74s4Y=; b=EKYSt669GtayTUQsrlAveV0lbXm9qqWdWIVs/FXjXQBS7Ytsf1Fz0Q4lq0nmt0XnB3 jFkPYV9F0v52xrE0MXo+SUQPpkuhnbX0jSNnhvrGS1N9uSBdfppUJYcpt/CnFxz1U6bD +jMTgjy82RWSadZxT0Gt91RAL+myB9k72nS+GTTxU2EM4GT5/a4X7bRojNPU7zisrm3M OE4gKwUcG5SmWIypY4O0q3Nq1lm4PMg+aPl7ZF6xuOgx8wa8HhcYLPBlkDksSwQHMka3 8rYJ8CBD++25sqrFMcvtGCU1kJQKohpuL2UX2spWc9FylTp0qfQPzeOkaJ/ox8O5hk9X P/Mg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Wv5CGmCHZ3hYfSsAGHVkQECZPH23IyQz8gOrwV74s4Y=; b=yz51vBYSQGsmhucAVZzCEE4w/kweKGmYN8mrETG/LddLkERnukwJPmtoBb5XwubVDr 48eic1b6NBc5RfxTPBTBYcJbTnLRkMjPFb9G9VFG/qK88z81nZQmkA0FH78HyfrzLumO yAx+YG04PkmXS8Xryqkn+DeddUGg6HTUU4JoBEWbmgxSuGbVK6i7nP3ebUzbyuXpnxRY 3vENKz3wpGNRjD64uhLj4poqeZNfwCQg9Isnxk/7hUYHDOOZYnhJEWsUIT48SzEjLt+l 0PZwA+tUCAGBM4RCZZj3803ZqD2Ul/DROgLBvfo72S/ZWmbyTeqVF/GHDcmu5NMtu4NJ dHag== X-Gm-Message-State: AOAM533nPUO4WPxnn4q7sDZ5XraoOBy2SBv7Xkv00/vFm6ME2g61ZwOe B+5ZGPlF63vBbsdeXCG80huTKULsQ4Jn+oISaR80EOp5AkY= X-Google-Smtp-Source: ABdhPJxm+tCWwhUUsaB3WkgX57ZO9dOfFFUYp8qsEAvfxAi7tkSDvtvE3wr4NBKAAWEbQIU3a8hz+CmH0nNGJwpY5Xo= X-Received: by 2002:a05:6808:f8e:: with SMTP id o14mr21676878oiw.33.1640810532340; Wed, 29 Dec 2021 12:42:12 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Richard Salz Date: Wed, 29 Dec 2021 15:42:01 -0500 Message-ID: To: Dan Cross Content-Type: multipart/alternative; boundary="000000000000ec887a05d44ef817" Subject: Re: [TUHS] moving directories in svr2 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 main list , Douglas McIlroy Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --000000000000ec887a05d44ef817 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable https://dsf.berkeley.edu/cs262/unix.pdf section 3.2 ends with: Each directory always has at least two entries. The name "." in each directory refers to the directory itself. Thus a program may read the current directory under the name =E2=80=9C.=E2=80=9D without knowing its complete path name. The name =E2=80=9C..=E2=80=9D by convention refers to the parent of the directory in which it appears, that is, to the directory in which it was created. The directory structure is constrained to have the form of a rooted tree. Except for the special entries =E2=80=9C.=E2=80=9D and = =E2=80=9C..=E2=80=9D, each directory must appear as an entry in exactly one other, which is its parent. The reason for this is to simplify the writing of programs which visit subtrees of the directory structure, and more important, to avoid the separation of portions of the hierarchy. If arbitrary links to directories were permitted, it would be quite difficult to detect when the last connection from the root to a directory was severed --000000000000ec887a05d44ef817 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Each directory always has at least two entrie= s. The
name "." in e= ach directory refers to the directory itself. Thus a
program may read the current directory under the nam= e =E2=80=9C.=E2=80=9D
without = knowing its complete path name. The name =E2=80=9C..=E2=80=9D by
convention refers to the parent of the d= irectory in which it
appears, = that is, to the directory in which it was created.
The directory structure is constrained to have the for= m
of a rooted tree. Except for= the special entries =E2=80=9C.=E2=80=9D and =E2=80=9C..=E2=80=9D,each directory must appear as an entry= in exactly one other,
which i= s its parent. The reason for this is to simplify the
writing of programs which visit subtrees of the dire= ctory
structure, and more impo= rtant, to avoid the separation of
portions of the hierarchy. If arbitrary links to directories
were permitted, it would be quite diffic= ult to detect when
the last co= nnection from the root to a directory was severed
--000000000000ec887a05d44ef817--