Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 6 Nov 2001 20:10:40 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 6 Nov 2001 20:10:30 -0500 Received: from sweetums.bluetronic.net ([66.57.88.6]:19864 "EHLO sweetums.bluetronic.net") by vger.kernel.org with ESMTP id ; Tue, 6 Nov 2001 20:10:13 -0500 Date: Tue, 6 Nov 2001 20:10:01 -0500 (EST) From: Ricky Beam X-X-Sender: To: cc: Linux Kernel Mail List Subject: Re: PROPOSAL: /proc standards (was dot-proc interface [was: /proc In-Reply-To: <3BE87CB9.43427FCF@evision-ventures.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 7 Nov 2001, Martin Dalecki wrote: >And then converted back to ASCII for printout on the terminal ;-). Well, they don't always get printf()'d... >The second problem is that /proc is one of the few design "inventions" in >linux, which didn't get copied over from some other UNIX box and Linus >doesn't wan't recognize that this was A BAD DESIGN CHOICE. /proc is a wonderful thing for what it was originally intended: access to the process table without looking at the tables in the kernel memory space (remember SunOS? what happened if /vmunix wasn't the running kernel?) Unfortunately, /proc has become the gheto of the Linux kernel. It is now the general dumping grounds for user/kernel interfacing. As a developer tool it's very handy; it's also very dangerous. Developers then resort to /proc as a perminant interface between kernel drivers and userland. (In the *BSD world, this is a kernfs, not a procfs.) For an example of /proc done right, find a Solaris box. What do you find in /proc? Gee, process information. Only process information. In. Binary. --Ricky - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/