From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1LoJdl-0002ip-Sy for mharc-grub-devel@gnu.org; Mon, 30 Mar 2009 11:43:09 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LoJdk-0002hR-O4 for grub-devel@gnu.org; Mon, 30 Mar 2009 11:43:08 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LoJdi-0002ei-UX for grub-devel@gnu.org; Mon, 30 Mar 2009 11:43:08 -0400 Received: from [199.232.76.173] (port=33584 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LoJdi-0002eL-L0 for grub-devel@gnu.org; Mon, 30 Mar 2009 11:43:06 -0400 Received: from mail.nexedi.com ([91.121.25.85]:35123 helo=nexedi.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LoJdi-00010F-AH for grub-devel@gnu.org; Mon, 30 Mar 2009 11:43:06 -0400 Received: from [10.8.0.46] (unknown [10.8.0.46]) by nexedi.com (Postfix) with ESMTP id C5E223D9EF for ; Mon, 30 Mar 2009 17:43:00 +0200 (CEST) From: "Yoshinori K. Okuji" Organization: enbug.org To: The development of GRUB 2 Date: Tue, 31 Mar 2009 00:42:53 +0900 User-Agent: KMail/1.9.10 References: <200903292354.48625.okuji@enbug.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200903310042.54616.okuji@enbug.org> X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) Subject: Re: [PATCH] Split of the normal mode 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: Mon, 30 Mar 2009 15:43:09 -0000 On Monday 30 March 2009 00:17:59 Bean wrote: > >> But how to store the parameters ? Boot media is not available, so we > >> can't read file, and we can't embed them in code. > > > > Could you be more specific? What case are you talking about? > > For example, something the boot modules can't detect boot partition > properly, such as some raid/lvm, etc. We might want to use uuid or > label to identify the partition. Then, there is a problem, how to > store the uuid value for the boot modules to use. > > Previously, I have thought of embedding a envblk in the kernel, then > modules can read variables at startup. But this method is quite > clumsy, and it needs to reserve valuable kernel size. Using a boot > script seems much flexible to me. Besides, it doesn't require > additional kernel space. The kernel can already parse commands in > rescue shell, I just reuse this function to run the boot script. I understand. Actually, GRUB Legacy has the same feature, named "preset menu", with which you can embed a config file in stage2. This feature is not used very much, because it requires recompilation in GRUB Legacy. > > Do you want to use GRUB without the scripting engine? > > The point is to support alternative script engine. Actually, I'm > thinking about integrating clisp into grub2. But some people may not > know about it, so they can still use the old bash engine. Sounds nice. :) But I still think that your patch splits into too many. If you split normal mode into: - a script module (sh.mod?) - a text menu module (menu.mod?) - the rest (normal.mod) then, that's fine. Regards, Okuji