From owner-freebsd-current  Mon Jun 16 13:24:42 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id NAA28377
          for current-outgoing; Mon, 16 Jun 1997 13:24:42 -0700 (PDT)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA28350;
          Mon, 16 Jun 1997 13:24:32 -0700 (PDT)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA18052; Mon, 16 Jun 1997 13:15:22 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199706162015.NAA18052@phaeton.artisoft.com>
Subject: Re: Need to rebuild libkvm,ps,w
To: msmith@atrad.adelaide.edu.au (Michael Smith)
Date: Mon, 16 Jun 1997 13:15:22 -0700 (MST)
Cc: hasty@rah.star-gate.com, dyson@FreeBSD.ORG, current@FreeBSD.ORG
In-Reply-To: <199706160147.LAA08666@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jun 16, 97 11:17:10 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > Dumb question, why can't we isolate the apps from the proc data structures?
> 
> Because the in-kernel infrastructure for arb. data retrieval isn't
> there yet.

Actually, isn't it really the memory image arguments to ps/w/et. al.
that cause the problem?  We could go to /proc tomorrow if /proc
were mandatory and we didn't care about ps'ing crash dumps (doing
that sems to me to be the job of the kernel debugger, anyway).


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.