Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 11 Nov 2002 20:42:35 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 11 Nov 2002 20:42:35 -0500 Received: from leibniz.math.psu.edu ([146.186.130.2]:23447 "EHLO math.psu.edu") by vger.kernel.org with ESMTP id ; Mon, 11 Nov 2002 20:42:34 -0500 Date: Mon, 11 Nov 2002 20:49:22 -0500 (EST) From: Alexander Viro To: Ryan Anderson cc: linux-kernel@vger.kernel.org Subject: Re: [RFC] devfs API In-Reply-To: <20021112013244.GF1729@mythical.michonline.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 Content-Length: 983 Lines: 27 On Mon, 11 Nov 2002, Ryan Anderson wrote: > On Sun, Nov 10, 2002 at 05:19:42PM -0500, Alexander Viro wrote: > > During the last couple of weeks I'd done a lot of digging in > > devfs-related code. Results are interesting, and not in a good sense. > > >From an outsider point of view (and because nobody else responded), I > think the big question here would be: Would you use it after this > cleanup? > > If you say yes, I'd say that's a good sign in its favor. The only way I'll use devfs is * on a separate testbox devoid of network interfaces * with no users * with no data - disk periodically populated from image on CD. And that's regardless of that cleanup - fixing the interface doesn't solve the internal races, so... - 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/