yes and no the original concept for multics was to have commands execute as separate subsidiary processes a la unix however multics processes turned out to be rather expensive computationally and so the plan was changed to make them subroutines called from the command interpreter the ability of multics to dynamically link to a subroutine in any 'file' in the filesystem was a key thing in making this work you could compile a new command and then try it out right away without having to link up a new version of the command interpreter multics did always have the ability for anyone to start a subsidiary process but it just wasn't used much talk