Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1GQEBK-0005Hz-46 for mharc-grub-devel@gnu.org; Wed, 20 Sep 2006 22:20:54 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GQEBI-0005HS-Fq for grub-devel@gnu.org; Wed, 20 Sep 2006 22:20:52 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GQEBG-0005GK-IP for grub-devel@gnu.org; Wed, 20 Sep 2006 22:20:51 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GQEBG-0005GF-CN for grub-devel@gnu.org; Wed, 20 Sep 2006 22:20:50 -0400 Received: from [212.85.152.101] (helo=kotoba.storever.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GQEEg-0003aR-16 for grub-devel@gnu.org; Wed, 20 Sep 2006 22:24:22 -0400 Received: from kotoba.oasis.nexedi.com (kotoba.oasis.nexedi.com [212.85.152.101]) by kotoba.storever.com (Postfix) with ESMTP id 819B23CBF63E8 for ; Thu, 21 Sep 2006 06:21:16 +0200 (CEST) Received: from [??1] (localhost [127.0.0.1]) by kotoba.storever.com (Postfix) with ESMTP id 1B5173CBF63E7 for ; Thu, 21 Sep 2006 06:21:16 +0200 (CEST) From: "Yoshinori K. Okuji" Organization: enbug.org To: The development of GRUB 2 Date: Thu, 21 Sep 2006 03:59:29 +0200 User-Agent: KMail/1.8.2 References: <20060917210823.GA22994@khazad.dyndns.org> <20060917212558.GA23125@khazad.dyndns.org> In-Reply-To: <20060917212558.GA23125@khazad.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200609210359.30068.okuji@enbug.org> X-Bogosity: No, tests=bogofilter, spamicity=0.473701, version=0.17.2 Subject: Re: [PATCH] Linux I2O devices X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Sep 2006 02:20:52 -0000 On Sunday 17 September 2006 23:25, Robert Millan wrote: > For I2O we have /dev/i2o/hd[a-z][0-9]. There's also a big family of device > sets using this scheme (/dev/*/hd[a-z][0-9]). Unless the second "if" can > be made the default option, we'll have to add knowledge of every of these > device paths here? If you think we can make this ugly code simpler and more consistent, let me know... Is there ever any rule in Linux?! Okuji