From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753815Ab0DSKmd (ORCPT ); Mon, 19 Apr 2010 06:42:33 -0400 Received: from ananke.wxnz.net ([58.28.4.122]:52852 "EHLO ananke.wxnz.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752433Ab0DSKmb (ORCPT ); Mon, 19 Apr 2010 06:42:31 -0400 X-Greylist: delayed 1323 seconds by postgrey-1.27 at vger.kernel.org; Mon, 19 Apr 2010 06:42:31 EDT From: skitching@apache.org To: jkt@gentoo.org To: linux-kernel@vger.kernel.org Subject: Re: boot device order troubleshooting without an initrd In-Reply-To: <20100418165125.1d2b2843@infradead.org> Date: Mon, 19 Apr 2010 22:20:23 +1200 Message-Id: <1271672423.005324.28333.nullmailer@xnet.co.nz> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org As it happens, I've been looking into this issue recently. [Warning: kernel newbie speaking!] Without an initrd, the options for the root= kernel parameters are only those supported in init/do_mount.c: 1. root=MAJOR:MINOR 2. root=integer where integer is MAJOR<