From owner-freebsd-questions Wed Nov 12 06:58:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA08450 for questions-outgoing; Wed, 12 Nov 1997 06:58:40 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA08430; Wed, 12 Nov 1997 06:58:35 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id GAA08154; Wed, 12 Nov 1997 06:50:22 -0800 (PST) Message-Id: <199711121450.GAA08154@implode.root.com> To: Zoltan Sebestyen cc: FreeBSD questions mailinglist , FreeBSD hackers mailinglist Subject: Re: Q: about procfs In-reply-to: Your message of "Wed, 12 Nov 1997 13:04:04 +0100." From: David Greenman Reply-To: dg@root.com Date: Wed, 12 Nov 1997 06:50:22 -0800 Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I'd like to know what will be the future of procfs on FreeBSD. Will it >provide more information about the system and the processes like it does >on Linux, or will I have to keep using kernel calls like the kvm_ >functions? This question raises everytime I port a Linux application that >uses procfs to gain some pieces of system level information. For most system information, I prefer the sysctl mechanism. For process information, I prefer procfs. We'll be extending both of these interfaces in the future to provide more information. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project