From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 7 Nov 2001 05:40:02 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 7 Nov 2001 05:39:52 -0500 Received: from [195.63.194.11] ([195.63.194.11]:27406 "EHLO mail.stock-world.de") by vger.kernel.org with ESMTP id ; Wed, 7 Nov 2001 05:39:46 -0500 Message-ID: <3BE91BD4.7A8BB3D9@evision-ventures.com> Date: Wed, 07 Nov 2001 12:32:36 +0100 From: Martin Dalecki Reply-To: dalecki@evision.ag X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.7-10 i686) X-Accept-Language: en, de MIME-Version: 1.0 To: Ricky Beam CC: dalecki@evision.ag, Linux Kernel Mail List Subject: Re: PROPOSAL: /proc standards (was dot-proc interface [was: /proc In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Ricky Beam wrote: > 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. Amen. I have enough of them at hand. And I don't miss any "wonderfull" functionality from linux /proc if I'm working on them.