From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1CsjFa-0006tQ-6E for mharc-grub-devel@gnu.org; Sun, 23 Jan 2005 10:02:02 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1CsjDy-0006DZ-5t for grub-devel@gnu.org; Sun, 23 Jan 2005 10:00:25 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1CsjDg-00067W-24 for grub-devel@gnu.org; Sun, 23 Jan 2005 10:00:06 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CsjDf-00064K-L9 for grub-devel@gnu.org; Sun, 23 Jan 2005 10:00:03 -0500 Received: from [212.43.237.68] (helo=kotoba.storever.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CsijE-0002EZ-7Q for grub-devel@gnu.org; Sun, 23 Jan 2005 09:28:36 -0500 Received: from ASSP-nospam (localhost [127.0.0.1]) by kotoba.storever.com (Postfix) with ESMTP id B4EBDF8E1B20 for ; Sun, 23 Jan 2005 15:28:35 +0100 (CET) Received: from 127.0.0.1 ([127.0.0.1] helo=localhost) by ASSP-nospam ; 23 Jan 05 14:28:35 -0000 From: "Yoshinori K. Okuji" Organization: enbug.org To: grub-devel@gnu.org Date: Sun, 23 Jan 2005 15:28:59 +0100 User-Agent: KMail/1.7.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501231528.59397.okuji@enbug.org> Subject: config file 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: Sun, 23 Jan 2005 15:02:00 -0000 I'd like to raise an issue about the config file. In GRUB Legacy, the structure of menu.lst is ugly, because it has a strange state when interpretting it. The semantics is that commands are executed until the first "title" is encounterred. Afterwards, commands are only "remembered" as boot entries. I think it would be more straightforward if commands are always executed. I'd like to redesign it in GRUB 2. One example is to write a boot entry like this: entry "GNU/Hurd" { root=(hd0,0) multiboot /boot/gnumach module /boot/serverboot ... } This idea is to make a boot entry a kind of shell function. What do you think? Okuji