Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 8 Nov 2001 03:56:47 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 8 Nov 2001 03:56:38 -0500 Received: from cc78409-a.hnglo1.ov.nl.home.com ([212.120.97.185]:28676 "EHLO dexter.hensema.xs4all.nl") by vger.kernel.org with ESMTP id ; Thu, 8 Nov 2001 03:56:23 -0500 From: spamtrap@use.reply-to (Erik Hensema) Subject: Re: Yet another design for /proc. Or actually /kernel. Date: 8 Nov 2001 08:56:21 GMT Message-ID: In-Reply-To: <20011108002705.A45912@compsoc.man.ac.uk> Reply-To: erik@hensema.net User-Agent: slrn/0.9.6.3 (Linux) To: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org John Levon (moz@compsoc.man.ac.uk) wrote: >On Wed, Nov 07, 2001 at 02:41:26PM -0500, William Knop wrote: > >> You really consider this discussion to be unimportant? Granted, the lack of >> organization in /proc is not a bug, but keeping the kernel organized is part >> of maintenence. Like cleaning my room-- it's not a showstopper if it is >> messy, but it is nicer and easier to work in when neat. > >Like cleaning your room, talking endlessly about how doesn't get you anywhere. >Show some code ... Just starting to code without giving much thought into it give us... the current /proc. It may be a good idea to actually design the thing this time. -- Erik Hensema (erik@hensema.net) I'm on the list, no need to Cc: me, though I appreciate one if your mailer doesn't support the References header. - 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/