The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] UNIX Backslash History
Date: Mon, 28 Oct 2019 11:51:44 -0400 (EDT)	[thread overview]
Message-ID: <20191028155144.ACBAB18C07E@mercury.lcs.mit.edu> (raw)

    > From: Charles Anthony

    >> I think it was >user_dir_dir>Group>User, wasn't it?

    > user_dir_dir>Project>User

Oh, right. Too many years spent on Unix! :-)

    > "Names" are aliases, similar to soft links

I feel like they are more similar to hard links; they belong to a segment, and
if the name is given to another segment, and the original segment has only
that name, it goes away. (See the discussion under "add_name" in the MPM
'Commands and Active Fuinctions'). Also, Multics does real soft links (too),
so names can't be soft links! :-)

	Noel

             reply	other threads:[~2019-10-28 15:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-28 15:51 Noel Chiappa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-10-27 21:31 Noel Chiappa
2019-10-27 21:51 ` Charles Anthony
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=20191028155144.ACBAB18C07E@mercury.lcs.mit.edu \
    --to=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).