From owner-freebsd-fs@FreeBSD.ORG Tue Feb 22 19:22:05 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF9801065670; Tue, 22 Feb 2011 19:22:05 +0000 (UTC) (envelope-from bfriesen@simple.dallas.tx.us) Received: from blade.simplesystems.org (blade.simplesystems.org [65.66.246.74]) by mx1.freebsd.org (Postfix) with ESMTP id 6F2B18FC12; Tue, 22 Feb 2011 19:22:05 +0000 (UTC) Received: from freddy.simplesystems.org (freddy.simplesystems.org [65.66.246.65]) by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id p1MJAv6s006999; Tue, 22 Feb 2011 13:10:57 -0600 (CST) Date: Tue, 22 Feb 2011 13:10:57 -0600 (CST) From: Bob Friesenhahn X-X-Sender: bfriesen@freddy.simplesystems.org To: John Baldwin In-Reply-To: <201102220931.17733.jhb@freebsd.org> Message-ID: References: <201102211707.p1LH7c8n075660@lurza.secnetix.de> <476667.58379.qm@web121516.mail.ne1.yahoo.com> <20110222095211.GA96223@icarus.home.lan> <201102220931.17733.jhb@freebsd.org> User-Agent: Alpine 2.01 (GSO 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (blade.simplesystems.org [65.66.246.90]); Tue, 22 Feb 2011 13:10:57 -0600 (CST) Cc: freebsd-fs@freebsd.org, Kelly Dean Subject: Re: Why is procfs deprecated in favor of procstat? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Feb 2011 19:22:06 -0000 On Tue, 22 Feb 2011, John Baldwin wrote: > > Actually, the replacement for procfs is not sysctl, but ptrace(2), and there I have been following this discussion with my jaw agape. It seems that the many men standing around this elephant are all perceiving completely different things based on their own interests and experiences. My own software is using procfs to efficiently determine the path to the currently running executable. I am sure that other software does the same since Linux procfs (and probably OS X) supports the same mechanism. It is difficult to imagine how this would be done via ptrace(2). Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/