Thou shalt have no other gods before the ANSI C standard 1567

however, there has been a lot written about a lot of the Multics being deployed in various (gov) environments where it was specifically used for isolation-parbreastioning of users.

frequently cited is the air force evoluation of multics (for gov. use) and the side note that it has no evidence of having buffer overlow situations (either from actual events or from detailed code reviews ... significantly contributing to this is that buffers and especially target buffers for copy operations carried explicit max. length values ... the semantics of which were supported by the infrastructure and libraries):

cp67 and vm370 in the commercial time-sharing deployments had significant requirements for sharing between (at least) subsets or collections of the online users (i.e. collections of users from the same corporation using the services). There were specific enhancements made by these service bureaus to accomplish such sharing (which didn't show back up in official product ... since they were viewed as commercial advantage).

note also that the original sql-relational database was built on vm-370 ... which had some number of enhancements for sharing, misc. system-r posts:

even tho the first commercial relational database was shipped on multics

i had done a lot at science center with paged mapped filesystem and sharing of file memory-mapped objects ... only a trivial small subset of which actually shipped in products:

some of which was used later at sjr in system-r work. in the tech. transfer of system-r to endicott for sql-ds ... they eventually regressed to wanting a version that didn't require any kernel changes, so it had to be mapped to less finer granularity sharing constructs.

--