From owner-freebsd-questions Sat Jan 13 13:25:49 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA13550 for questions-outgoing; Sat, 13 Jan 1996 13:25:49 -0800 (PST) Received: from fslg8.fsl.noaa.gov (fslg8.fsl.noaa.gov [137.75.131.171]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA13545 for ; Sat, 13 Jan 1996 13:25:44 -0800 (PST) Received: by fslg8.fsl.noaa.gov (5.57/Ultrix3.0-C) id AA11932; Sat, 13 Jan 96 15:25:43 -0600 Received: by emu.fsl.noaa.gov (1.38.193.4/SMI-4.1 (1.38.193.4)) id AA08589; Sat, 13 Jan 1996 14:25:42 -0700 Date: Sat, 13 Jan 1996 14:25:42 -0700 From: kelly@fsl.noaa.gov (Sean Kelly) Message-Id: <9601132125.AA08589@emu.fsl.noaa.gov> To: peterb@telerama.lm.com Cc: questions@freebsd.org In-Reply-To: (message from Peter Berger on Sat, 13 Jan 1996 15:16:03 -0500 (EST)) Subject: Re: ProcFS Sender: owner-questions@freebsd.org Precedence: bulk >>>>> "Peter" == Peter Berger writes: Peter> What is Procfs Process filesystem ... a way of representing running programs as nodes in the filesystem tree. Peter> and do I care? That's up to you, really. Peter> If I'm not examining the state of processes by hand, does Peter> it offer any performance improvement? The performance improvement I could see is reduced programmer's time accessing this information. Peter> Why should I keep this configured into a kernel? You shouldn't. It works just fine as an automatically loaded kernel module. It's not in my kernel and yet ``cat /proc/curproc/status'' works just fine. -- Sean Kelly NOAA Forecast Systems Laboratory, Boulder Colorado USA Shelve all your books with the spines facing the wall. Complain loudly that you can never find the book that you want. -- One of 120 ways to annoy your roommate.