🚀 go-pugleaf

David Kastrup wrote:
> =

> Vince Scarafino <vscarafi@ford.com> writes:
> =

> > Christopher Grayce wrote:
> > >
> > > Something interesting to me is that Multics had full
> > > commands as well as the abbreviations, e.g.
> > >
> > > print_working_directory   <->    pwd
> > >
> > > You could use either.  Funny that now when we can much
> > > more easily afford the overhead to have both it's not
> > > done.
> > >
> > > CJG
> >
> > That's because Multics supported the concept of "adnames," which
> > allowed a file to have multiple names associated with it.  The
> > neat thing about this was that in many instances, you could
> > type out what you were looking for (using the underscore to
> > represent a blank between words) and you'd actually find out
> > there was a command with that name and it answered your question.
> > Adname support is something I miss.  Soft links in unix have
> > subtle differences that drive you crazy if you try to use them
> > for this purpose.
> =

> Then use hard links. "a file having multiple names associated with it"
> is hard links, quite clearly.

Not quite. If I create a hard link to /bin/pwd named
"print_working_directory", and then I remove /bin/pwd,
I still have the file. Does it work the same way with
Multics' "file having multiple names associated with it"?
It looks to me like that would be one file, such that if
I remove any, they all vanish. "subtle differences".
Of course, I could be wrong.

> =

> --
> David Kastrup                                     Phone: +49-234-700-55=
70
> Email: dak@neuroinformatik.ruhr-uni-bochum.de       Fax: +49-234-709-42=
09
> Institut f=FCr Neuroinformatik, Universit=E4tsstr. 150, 44780 Bochum, G=
ermany

-- =

Elchonon Edelson	wanderer@isoft.com
IntelliSoft Corp.	http://www.isoft.com/