From: charles.unix.pro@gmail.com (Charles Anthony)
Subject: [TUHS] the guy who brought up SVr4 on Sun machines
Date: Wed, 11 Jan 2017 11:37:18 -0800 [thread overview]
Message-ID: <CANV78LTgFQPcY3dv7c4wGEa9YiDUfeeEz1xT7gbiPv=8puYV=Q@mail.gmail.com> (raw)
In-Reply-To: <20170111180721.0FBB018C08B@mercury.lcs.mit.edu>
On Wed, Jan 11, 2017 at 10:07 AM, Noel Chiappa <jnc at mercury.lcs.mit.edu>
wrote:
> > 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.
>
>
'pdd' also contained temporary segments, ala mktemp:
r 11:33 0.092 1
cwd [pd]
r 11:33 0.086 3
ls
Segments = 21, Lengths = 0.
0 !BBBKLDJkqPKWqL.area.linker
0 stack_1
r w 0 archive_temp_.archive
rew 0 !BBBKLDJkqGGBMh.temp.0346
rew 0 !BBBKLDJkqGFKDc.temp.0345
rew 0 !BBBKLDJkqGDWMn.temp.0344
rew 0 !BBBKLDJkqGCfXX.temp.0343
rew 0 !BBBKLDJkqGBpDB.temp.0342
rew 0 !BBBKLDJkqGBCwg.temp.0341
rew 0 !BBBKLDJkqFzFDz.temp.0340
rew 0 !BBBKLDJkqFxMcW.temp.0337
rew 0 !BBBKLDJkpmxKqH.temp.0332
rew 0 !BBBKLDJkpmwMfz.temp.0331
r w 0 process_search_segment_.4
rew 0 !BBBKLDJknDXFNp.temp.0304
rew 0 !BBBKLDJknCfjfK.area.linker
rew 0 stack_4
re 0 pit
0 pds
0 kst
0 dseg
r 11:33 0.214 0
-- Charles
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170111/ce4fcf2e/attachment.html>
next prev parent reply other threads:[~2017-01-11 19:37 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 18:07 Noel Chiappa
2017-01-11 19:37 ` Charles Anthony [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-01-10 21:26 Noel Chiappa
2017-01-10 15:38 Noel Chiappa
2017-01-10 15:12 Berny Goodheart
2017-01-10 16:03 ` arnold
2017-01-10 16:20 ` Larry McVoy
2017-01-10 16:24 ` Joerg Schilling
2017-01-10 16:32 ` Berny Goodheart
2017-01-10 16:40 ` Chet Ramey
2017-01-10 16:41 ` Joerg Schilling
2017-01-10 16:20 ` Joerg Schilling
2017-01-10 16:34 ` Clem cole
2017-01-10 16:38 ` Chet Ramey
2017-01-10 16:57 ` Berny Goodheart
2017-01-10 17:10 ` Joerg Schilling
2017-01-10 17:47 ` Warner Losh
2017-01-10 18:28 ` Larry McVoy
2017-01-10 18:33 ` Warner Losh
2017-01-10 18:42 ` Larry McVoy
2017-01-10 19:21 ` Clem cole
2017-01-10 19:41 ` Clem cole
2017-01-11 21:03 ` Dan Cross
2017-01-11 20:56 ` Dan Cross
2017-01-11 22:57 ` Joerg Schilling
2017-01-11 23:06 ` Larry McVoy
2017-01-11 23:52 ` Joerg Schilling
2017-01-11 23:57 ` Larry McVoy
2017-01-12 0:07 ` Joerg Schilling
2017-01-12 1:58 ` Larry McVoy
2017-01-12 10:39 ` Joerg Schilling
[not found] ` <1154c8d8-2051-455e-a3f2-45415d901232.maildroid@localhost>
2017-01-10 16:34 ` Berny Goodheart
2017-01-04 2:41 Larry McVoy
2017-01-04 3:00 ` Warner Losh
2017-01-04 3:23 ` Dan Cross
2017-01-04 3:35 ` Larry McVoy
2017-01-04 12:24 ` Ed Carp
2017-01-04 16:17 ` ron minnich
2017-01-04 16:31 ` Joerg Schilling
2017-01-04 16:34 ` ron minnich
2017-01-04 16:57 ` Joerg Schilling
2017-01-04 17:06 ` Larry McVoy
2017-01-04 17:11 ` Joerg Schilling
2017-01-04 17:15 ` Larry McVoy
2017-01-04 17:40 ` Joerg Schilling
2017-01-04 17:42 ` Larry McVoy
2017-01-04 17:48 ` Joerg Schilling
2017-01-04 17:57 ` Larry McVoy
2017-01-04 18:24 ` Dan Cross
2017-01-04 18:30 ` Dan Cross
2017-01-04 18:25 ` Joerg Schilling
2017-01-04 18:32 ` Joerg Schilling
2017-01-04 18:46 ` Dan Cross
2017-01-05 11:18 ` Joerg Schilling
2017-01-06 2:09 ` Larry McVoy
2017-01-06 3:07 ` Steve Nickolas
2017-01-06 17:38 ` Warner Losh
2017-01-04 17:36 ` ron minnich
2017-01-04 17:41 ` Joerg Schilling
2017-01-04 16:46 ` Larry McVoy
2017-01-04 17:02 ` Joerg Schilling
2017-01-04 17:10 ` Larry McVoy
2017-01-04 17:39 ` Joerg Schilling
2017-01-04 17:52 ` Larry McVoy
2017-01-04 18:23 ` Joerg Schilling
2017-01-04 18:27 ` Larry McVoy
2017-01-04 18:29 ` Joerg Schilling
2017-01-04 18:44 ` Larry McVoy
2017-01-05 11:50 ` Joerg Schilling
2017-01-06 2:02 ` Larry McVoy
2017-01-09 13:40 ` Joerg Schilling
2017-01-09 17:48 ` Larry McVoy
2017-01-10 3:58 ` Larry McVoy
2017-01-10 4:16 ` Warner Losh
2017-01-08 1:37 ` Larry McVoy
2017-01-05 2:26 ` Wesley Parish
2017-01-04 18:56 ` Nevin Liber
2017-01-04 19:05 ` Warner Losh
2017-01-04 20:00 ` Clem Cole
2017-01-04 21:20 ` Brad Spencer
2017-01-04 21:57 ` William Pechter
2017-01-04 21:57 ` William Pechter
2017-01-05 0:36 ` Dave Horsfall
2017-01-05 0:43 ` Larry McVoy
2017-01-05 0:50 ` William Pechter
2017-01-05 1:01 ` Larry McVoy
2017-01-05 3:00 ` Wesley Parish
2017-01-05 3:13 ` Larry McVoy
2017-01-05 8:12 ` Andy Kosela
2017-01-05 16:23 ` Larry McVoy
2017-01-05 16:31 ` Clem Cole
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANV78LTgFQPcY3dv7c4wGEa9YiDUfeeEz1xT7gbiPv=8puYV=Q@mail.gmail.com' \
--to=charles.unix.pro@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).