The UNIX system has been in wide use for over 20 years, and has helped to define many areas of computing.
holy shit they made a virtual chroot for subprocess execution. THESE MOTHERFUCKERS MADE DOCKER!
Basically the scheme consists of four parts:
I'M READY I'M FUCKING READY
so like not only does clearly hint at some of the work we would do like 40 years later with spack to codify shared library ABI, you could even argue for the direct thread from this to my proposal to systemd to force upfront declaration of their dlopen() deps!!
![Basically the scheme consists of four parts:
a. Make the globally unique name of the object
in question refer to a special kind of directory (hereafter referred to as a hidden directory] instead of the object itself.
b. Inside this directory put the different versions of the file, naming them based on the
context with which they are associated. For
example, have the command /bin/who be a
hidden directory with the file entries ~5 and
vaz that are the respective load modules.
c. Keep a per-process inherited context for
these hidden directories. If a hidden directory is found during pathname searching (see
section 4.4 for pathname searching), it is examined for a match with the process's context rather than the next component of the
pathnames passed to the system.
d. Give users and programs an escape mechanism to make hidden directories visible so
they can be examined and specific entries
manipulated.](https://asset.circumstances.run/media_attachments/files/116/592/086/818/798/340/original/0a1353421e8be56e.png)
a special kind of directory (hereafter referred to as a hidden directory)
nobody talks about this
Keep a per-process inherited context for these hidden directories.
this is specifically for ABI translation. this is pretty obviously the future
Give users and programs an escape mechanism to make hidden directories visible so they can be examined and specific entries manipulated.
this is literally something pouzin has literally said
not only does this naming scheme allow us to store and name load modules for different sites, but allows us to transparently run a requested command on the site for which a load module exists.
multiplatform binary!!!!! fat pex files!!!!!!
the pants guy and i worked on a groundbreaking fucking project together right as i left twitter very similar to this local module resolution work (it involved the network too) and we both found each other working on very similar followup projects several years later
nerd sniping john sirois is one of my proudest feats
omg bruh
The only exception is remote access to raw, non-character devices and these can be accessed by executing processes remotely.
THEY DID RPC IN 1981!!!! I DID RPC IN 2021!!!!
Interprocess communication (ipc) is often a controversial subject in a single machine operating system, with many differing opinions.
In a distributed environment, the requirements of error handling impose a number of additional requirements that help make design decisions, potentially easing disagreements.
"yeah we were too busy solving hard problems to disagree"
In LOCUS, the initial ipc effort was further simplified by the desire to provide a network-wide ipc facility which is fully compatible with the single machine functions that were already present in Unix.
FUCK i really badly need to do something this cool again so i can say a line this hot
Their semantics in LOCUS are identical to those seen on a single machine Unix system, even when processes are resident on different machines in LOCUS.
every NFS mount ever spontaneously returns SIGBUS
ok i absolutely need to find this dissertation they just cited
Walker, B.J., Issues of Network Transparency and File Replication in Distributed Systems: LOCUS, Ph.D. Dissertation, Computer Science Department, University of California, Los Angeles, 1983
