The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] Dash options
Date: Wed, 29 Nov 2017 09:03:26 -0500 (EST)	[thread overview]
Message-ID: <20171129140326.6298D18C096@mercury.lcs.mit.edu> (raw)

    > From: Charles Anthony

    > Entry points are usually defined as "foo$bar", where "foo" is the
    > segment name, and "bar" an entry point in the segment symbol table. I
    > believe that the degerate case of "foo$" is treated as "foo$foo" by the
    > shell.

So I'm curious about how this, and additional names, interact. (For those who
aren't familiar with Multics, a segment [file, sort of] can have multiple
names. This is sort of like 'hard links' in Unix, except that in Multics one
name, the "primary name" is very slightly preeminent. See here:

  http://web.mit.edu/multics-history/source/Multics/mdds/mdd006.compout

page 2-5, for more, if you're interested.)

So if I have a segment with primary name 'foo', and additional names 'bar' and
'zap', and I say 'zap' to the Multics shell, I assume it does a call to
zap$zap, which finds the segment with the primary name 'foo', and calls the
'zap' entry therein?


    > Multics rulez; UNIX droolz

Dude, you clearly have Very Large brass ones to send that to this list! :-)

      Noel


             reply	other threads:[~2017-11-29 14:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-29 14:03 Noel Chiappa [this message]
2017-11-29 20:29 ` Charles Anthony
  -- strict thread matches above, loose matches on Subject: below --
2017-11-29  1:23 Doug McIlroy
2017-11-29  1:37 ` George Michaelson
2017-11-29  2:22 ` Charles Anthony
     [not found] <mailman.376.1511899437.9955.tuhs@minnie.tuhs.org>
2017-11-28 21:30 ` Paul Ruizendaal
2017-11-28 13:19 Noel Chiappa
2017-11-28 18:20 ` Clem Cole
2017-11-28 21:56   ` Dave Horsfall
2017-11-28  5:51 Jon Steinhart
2017-11-28  6:05 ` Dave Horsfall
2017-11-28  6:49   ` Andrew Warkentin
2017-11-28 11:18     ` Ralph Corderoy
2017-11-28 11:49       ` Michael Kjörling
2017-11-28 12:46         ` Ralph Corderoy
2017-11-28 18:01       ` Lawrence Stewart
2017-11-28 19:36     ` Paul Winalski
2017-11-28 20:03       ` Clem Cole
2017-11-28  6:28 ` Greg 'groggy' Lehey
2017-11-29 19:16   ` Steffen Nurpmeso
     [not found]     ` <20171204054651.GA17671@eureka.lemis.com>
     [not found]       ` <20171204215701.l9Pvr%steffen@sdaoden.eu>
2017-12-05 13:22         ` Steffen Nurpmeso
2017-12-07  5:15           ` Greg 'groggy' Lehey

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=20171129140326.6298D18C096@mercury.lcs.mit.edu \
    --to=jnc@mercury.lcs.mit.edu \
    /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).