From: Charles Anthony <charles.unix.pro@gmail.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] UNIX Backslash History
Date: Sun, 27 Oct 2019 14:51:28 -0700 [thread overview]
Message-ID: <CANV78LSdkPj-tc=ezHfSgWU0PYriDJ86HRR0WA7fvh44su8pAw@mail.gmail.com> (raw)
In-Reply-To: <20191027213133.9907E18C083@mercury.lcs.mit.edu>
[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]
On Sun, Oct 27, 2019 at 2:31 PM Noel Chiappa <jnc@mercury.lcs.mit.edu>
wrote:
> > From: Charles Anthony
>
> > /home/CAnthony
>
> I think it was >user_dir_dir>Group>User, wasn't it? I seem to remember my
> homedir on MIT-Multics was >udd>CSR>JNChiappa?
>
>
>user_dir_dir>Project>User
>user_dir_dir Home directories of users
>daemon_dir_dir Home directories of daemons
>process_dir_dir /proc
"Names" are aliases, similar to soft links; "udd" is a name for
"user_dir_dir" so ">udd" and ">user_dir_dir" point to the same directory.
>user_dir_dir>SysAdmin>admin or >udd>sa>a is ~root/
Circulating back to the original question, backslash is used as an escape
character on Multics. "\f" is end-of-file-ish, used eg to leave input mode
in text editors.
-- Charles
And I wonder if the 'dd' directory on PDP-7 Unix owe anything to 'udd'?
>
> Getting back to the original query, I'm wondering if '/' was picked
> as it wasn't shifted, unlike '>'?
>
> Noel
>
--
X-Clacks-Overhead: GNU Terry Pratchett
[-- Attachment #2: Type: text/html, Size: 2083 bytes --]
next prev parent reply other threads:[~2019-10-27 21:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-27 21:31 Noel Chiappa
2019-10-27 21:51 ` Charles Anthony [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-28 15:51 Noel Chiappa
2019-10-27 20:31 Doug McIlroy
2019-10-27 20:42 ` Richard Salz
2019-10-27 20:49 ` Charles Anthony
2019-10-27 23:01 ` Grant Taylor via TUHS
2019-10-28 1:11 ` Steve Nickolas
2019-10-28 12:00 ` Michael Kjörling
2019-10-28 13:44 ` Clem Cole
2019-10-28 15:08 ` Steve Nickolas
2019-10-28 18:47 ` Dave Horsfall
2019-10-28 20:43 ` Paul Winalski
2019-10-27 20:46 ` Bakul Shah
2019-10-28 17:36 ` Anthony Martin
2019-10-28 18:17 ` Charles Anthony
2019-10-26 9:39 Caipenghui
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='CANV78LSdkPj-tc=ezHfSgWU0PYriDJ86HRR0WA7fvh44su8pAw@mail.gmail.com' \
--to=charles.unix.pro@gmail.com \
--cc=jnc@mercury.lcs.mit.edu \
--cc=tuhs@tuhs.org \
/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).