Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756697AbYFCLKH (ORCPT ); Tue, 3 Jun 2008 07:10:07 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751927AbYFCLJ5 (ORCPT ); Tue, 3 Jun 2008 07:09:57 -0400 Received: from sovereign.computergmbh.de ([85.214.69.204]:35569 "EHLO sovereign.computergmbh.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751919AbYFCLJ5 (ORCPT ); Tue, 3 Jun 2008 07:09:57 -0400 Date: Tue, 3 Jun 2008 13:09:55 +0200 (CEST) From: Jan Engelhardt To: Nick Piggin cc: Petr Tesarik , Christoph Hellwig , torvalds@osdl.org, linux-kernel@vger.kernel.org Subject: Re: Why is the rewritten ramdisk driver called brd instad of rd In-Reply-To: <20080528061130.GB16441@wotan.suse.de> Message-ID: References: <20080321130552.GA28274@lst.de> <1211880480.29836.11.camel@elijah.suse.cz> <20080528061130.GB16441@wotan.suse.de> User-Agent: Alpine 1.10 (LNX 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1079 Lines: 26 On Wednesday 2008-05-28 08:11, Nick Piggin wrote: >On Tue, May 27, 2008 at 11:28:00AM +0200, Petr Tesarik wrote: >> On Fri, 2008-03-21 at 14:05 +0100, Christoph Hellwig wrote: >> > Any reason why the rewritten ramdisk driver has a new name? It's for >> > all matters an inplace replacement of the old rd driver so it should >> > be called rd.c / rd.ko to not confused instaler/developers/etc. >> >> I think it's because the old rd played some dirty tricks with the page >> cache, while the reworked one is a straightforward implementation of a >> normal _b_lock device -> hence the "b". >> >> No guarantee of correctness. > >Yeah it was a rwrite from scratch and it lived with the rd.c code for >a while (although maybe never in mainline). I guess it might be good >idea to rename it back to rd? Just add a MODULE_ALIAS("rd"). -- 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/