> I wonder if >pdd ... was in any way any inspiration for /proc?
That may have been a bit too cryptic. "pdd" ('process directory directory')
was a top-level directory in the Multics filesystem which contained a
directory for each process active in the system; each directory contained data
(in segments - roughly, 'files', but Multics didn't have files because it was
a single-level store system) associated with the process, such as its kernel-
and user-mode (effectively - technically, ring-0 and ring-4) stacks, etc.
So if a process was sitting in a system call, you could go into the right
directory in >pdd and look at its kernel stack and see the sequence of
procedure calls (with arguments) that had led it to the point where it
blocked. Etc, etc.
r 11:33 0.092 1cwd [pd]r 11:33 0.086 3lsSegments = 21, Lengths = 0.0 !BBBKLDJkqPKWqL.area.linker0 stack_1r w 0 archive_temp_.archiverew 0 !BBBKLDJkqGGBMh.temp.0346rew 0 !BBBKLDJkqGFKDc.temp.0345rew 0 !BBBKLDJkqGDWMn.temp.0344rew 0 !BBBKLDJkqGCfXX.temp.0343rew 0 !BBBKLDJkqGBpDB.temp.0342rew 0 !BBBKLDJkqGBCwg.temp.0341rew 0 !BBBKLDJkqFzFDz.temp.0340rew 0 !BBBKLDJkqFxMcW.temp.0337rew 0 !BBBKLDJkpmxKqH.temp.0332rew 0 !BBBKLDJkpmwMfz.temp.0331r w 0 process_search_segment_.4rew 0 !BBBKLDJknDXFNp.temp.0304rew 0 !BBBKLDJknCfjfK.area.linkerrew 0 stack_4re 0 pit0 pds0 kst0 dsegr 11:33 0.214 0