Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S271365AbTHHPXo (ORCPT ); Fri, 8 Aug 2003 11:23:44 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S271378AbTHHPXo (ORCPT ); Fri, 8 Aug 2003 11:23:44 -0400 Received: from rwcrmhc13.comcast.net ([204.127.198.39]:63135 "EHLO rwcrmhc13.comcast.net") by vger.kernel.org with ESMTP id S271365AbTHHPXn (ORCPT ); Fri, 8 Aug 2003 11:23:43 -0400 Date: Fri, 8 Aug 2003 08:23:37 -0700 From: "H. J. Lu" To: Herbert Xu Cc: linux-kernel@vger.kernel.org Subject: Re: Initrd problem with 2.6 kernel Message-ID: <20030808152337.GA11088@lucon.org> References: <20030807223019.GA27359@lucon.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 917 Lines: 22 On Fri, Aug 08, 2003 at 08:49:16PM +1000, Herbert Xu wrote: > H. J. Lu wrote: > > There is a chicken and egg problem with initrd on 2.6. When > > root=/dev/xxx is passed to kernel, kernel will call try_name, which > > uses /sys/block/drive/dev, to find out the device number for ROOT_DEV. > > The problem is /sys/block/drive may not exist if the driver is loaded > > by /linuxrc in initrd. As the result, /linuxrc can't use > > /proc/sys/kernel/real-root-dev to determine the root device number. > > You can replicate the sysfs probing in userspace. I did that in > Debian initrd-tools 0.1.51. It sounds a good idea. I will give it a try. Thanks. H.J. - 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/