Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S271073AbTHGWa2 (ORCPT ); Thu, 7 Aug 2003 18:30:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S271080AbTHGWa1 (ORCPT ); Thu, 7 Aug 2003 18:30:27 -0400 Received: from rwcrmhc11.comcast.net ([204.127.198.35]:43986 "EHLO rwcrmhc11.comcast.net") by vger.kernel.org with ESMTP id S271073AbTHGWa1 (ORCPT ); Thu, 7 Aug 2003 18:30:27 -0400 Date: Thu, 7 Aug 2003 15:30:19 -0700 From: "H. J. Lu" To: linux kernel Subject: Initrd problem with 2.6 kernel Message-ID: <20030807223019.GA27359@lucon.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 645 Lines: 14 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. 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/