The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@bitblocks.com>
To: Norman Wilson <norman@oclsc.org>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] 4.1c bsd ptrace man entry ("ptrace is unique and arcane")
Date: Tue, 25 Jun 2019 12:42:07 -0700	[thread overview]
Message-ID: <D3DF665F-0095-47C4-8D1D-BD1036F71E5F@bitblocks.com> (raw)
In-Reply-To: <1561491205.19116.for-standards-violators@oclsc.org>

On Jun 25, 2019, at 12:33 PM, Norman Wilson <norman@oclsc.org> wrote:
> 
> It's interesting that this comment about ptrace was written
> as early as 1980.
> 
> Ron Minnich's reference to Plan 9 /proc misses the mark, though.
> By the time Plan 9 was written, System V already had /proc; see
> 
> https://www.usenix.org/sites/default/files/usenix_winter91_faulkner.pdf
> 
> And as the authors say, the idea actually dates back to Tom Killian's
> /proc in Research UNIX.  I don't know when Tom's code first went
> live, but I first heard about it by seeing it in action on my first
> visit to Bell Labs in early 1984, and it was described in public in
> a talk at the Summer 1984 USENIX conference in Salt Lake City.
> I cannot quickly find an online copy of the corresponding paper;
> pointers appreciated.  (Is there at least an online index of BTL
> CSTRs?  The big search engine run by the place that still has
> some 1127 old-timers can't find that either.)

http://lucasvr.gobolinux.org/etc/Killian84-Procfs-USENIX.pdf



  reply	other threads:[~2019-06-25 19:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-25 19:33 Norman Wilson
2019-06-25 19:42 ` Bakul Shah [this message]
2019-06-25 20:35 ` Clem Cole
2019-06-25 23:52 ` ron minnich
2019-06-26  0:37   ` Rob Pike
2019-06-26  0:46     ` Larry McVoy
2019-06-26  0:56       ` Rob Pike
2019-06-26  1:03       ` ron minnich
2019-06-26  1:12         ` George Michaelson
2019-06-26  1:32           ` Noel Hunt
2019-06-26 15:41         ` Theodore Ts'o
  -- strict thread matches above, loose matches on Subject: below --
2019-06-25  2:27 Kirk McKusick
2019-06-25  1:08 ron minnich

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=D3DF665F-0095-47C4-8D1D-BD1036F71E5F@bitblocks.com \
    --to=bakul@bitblocks.com \
    --cc=norman@oclsc.org \
    --cc=tuhs@tuhs.org \
    /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).