From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.33) id 1BY14n-00067L-QI for mharc-grub-devel@gnu.org; Wed, 09 Jun 2004 07:17:02 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BY14m-00065j-6o for grub-devel@gnu.org; Wed, 09 Jun 2004 07:17:00 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BY14k-00064Z-Vk for grub-devel@gnu.org; Wed, 09 Jun 2004 07:16:59 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BY14k-000615-QL for grub-devel@gnu.org; Wed, 09 Jun 2004 07:16:58 -0400 Received: from [212.43.237.68] (helo=kotoba.storever.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BY13a-0008Qw-M0 for grub-devel@gnu.org; Wed, 09 Jun 2004 07:15:47 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by kotoba.storever.com (Postfix) with ESMTP id 9019315F5281A for ; Wed, 9 Jun 2004 07:15:43 -0400 (EDT) From: "Yoshinori K. Okuji" Organization: enbug.org To: The development of GRUB 2 Date: Wed, 9 Jun 2004 13:19:34 +0200 User-Agent: KMail/1.5.3 References: <20040601121704.GA4680@artax.karlin.mff.cuni.cz> <200406041324.42057.okuji@enbug.org> <20040606105515.GA25078@artax.karlin.mff.cuni.cz> In-Reply-To: <20040606105515.GA25078@artax.karlin.mff.cuni.cz> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200406091319.34017.okuji@enbug.org> Subject: Re: normal vs. rescue mode commands X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.4 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: Wed, 09 Jun 2004 11:17:00 -0000 On Sunday 06 June 2004 12:55, Tomas Ebenlendr wrote: > > 1. Generate two versions for each loader from the same source code. > > > > This case compiles the same source code twice to generate two > > different loaders for rescue mode and normal mode. Basically, the > > version for rescue mode would be a subset of the version for normal > > mode. This makes redundant binary code, but the maintainability is > > not very bad. > > This looks like best solution for me, also the 'normal' mode loader > may depend on 'rescue' mode loader and use some of its functions. > This looks like most 'clean' way. If we want that users won't be > confused by 2 modules doing the same, we can add 'automatic module > load support' which will load modules-normal_mode_extensions of > loaded loaders to normal mode. Ok. As others seem to have no opinion, let's go in this way. Then, how about the naming convention? We need to have a standard way to distinguish between normal mode loaders and rescue mode loaders by file names. That is why I prefixed loaders with '_'. But I don't think an underscore is so good. And, at the same time, I'd like to make all filenames fit into the DOS-style (8.3 filenames), so that we don't need to use VFAT on FAT filesystems. I think this is better, because Microsoft claims that they have a software patent about the long filename extension... *sigh* What do you think? Okuji