Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S269380AbUICIcL (ORCPT ); Fri, 3 Sep 2004 04:32:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S269394AbUICIcK (ORCPT ); Fri, 3 Sep 2004 04:32:10 -0400 Received: from mail.kroah.org ([69.55.234.183]:16786 "EHLO perch.kroah.org") by vger.kernel.org with ESMTP id S269380AbUICIZ6 (ORCPT ); Fri, 3 Sep 2004 04:25:58 -0400 Date: Fri, 3 Sep 2004 10:22:57 +0200 From: Greg KH To: Jamie Lokier Cc: Horst von Brand , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, reiserfs-list@namesys.com Subject: Re: silent semantic changes with reiser4 Message-ID: <20040903082256.GA17629@kroah.com> References: <200408290004.i7T04DEO003646@localhost.localdomain> <20040901224513.GM31934@mail.shareable.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040901224513.GM31934@mail.shareable.org> User-Agent: Mutt/1.5.6i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 990 Lines: 25 On Wed, Sep 01, 2004 at 11:45:13PM +0100, Jamie Lokier wrote: > Horst von Brand wrote: > > What happened to "code talks, bullshit walks"? > > devfs is a fine example of why code isn't enough. With devfs the code > came first, the >1 year of strategic bullshit politics from the "it's > not traditional unix" crowd came later, then it went in, then lots of > people used it, then it was replaced by something which still doesn't > work as well as 2.4 does with or without devfs, and people are still > using it despite it's faults. What is udev's faults that have an issue with? Yes, we don't do module autoloading when opening a device node, but that's well known, documented, and the way the kernel has evolved to anyway. thanks, greg k-h - 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/