From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Hyp45-0001IS-R8 for mharc-grub-devel@gnu.org; Thu, 14 Jun 2007 09:08:41 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Hyp44-0001H7-EH for grub-devel@gnu.org; Thu, 14 Jun 2007 09:08:40 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Hyp40-0001D1-Qy for grub-devel@gnu.org; Thu, 14 Jun 2007 09:08:40 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Hyp40-0001Co-Iy for grub-devel@gnu.org; Thu, 14 Jun 2007 09:08:36 -0400 Received: from m15-111.126.com ([220.181.15.111]) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1Hyp3z-0005Rd-BS for grub-devel@gnu.org; Thu, 14 Jun 2007 09:08:36 -0400 Received: from localhost (unknown [123.49.202.64]) by smtp1 (Coremail) with SMTP id wKjJCygA_kPNPXFGDxZkBg==.17047S2; Thu, 14 Jun 2007 21:08:30 +0800 (CST) Date: Thu, 14 Jun 2007 21:08:09 +0800 From: Bean To: The development of GRUB 2 Message-ID: <20070614130809.GA736@ws3.vdp.com> References: <20070614034649.GA591@ws3.vdp.com> <20070614060809.GA27145@aragorn> <20070614062451.GA591@ws3.vdp.com> <871wgex473.fsf@xs4all.nl> <20070614102419.GA633@ws3.vdp.com> <87sl8uvmix.fsf@xs4all.nl> <20070614113154.GA686@ws3.vdp.com> <87odjivjox.fsf@xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87odjivjox.fsf@xs4all.nl> User-Agent: Mutt/1.5.13 (2006-08-11) X-Coremail-Antispam: 1U3Yxn0WfASr-VFAUDIcSsGvfJTRUUUj8xFxVCF77xC6IxKo4 kEV4ylIxAIcVC2z280aVAFwI0_Jr0_Gr1lnxkEFVAIw20F6cxK64vIFxWlx4CE17CEb7AF 67AKxVWUJVWUXwCjxxvEw4Wle4C267I2x7xF54xIwI1lYx0E2Ix0cI8IcVAFwI0_Jr0_Jr 4l4x8a6c8ajcxJMcIj6I8E87Iv67AKxVWUJVW8JwAFxVCaYxvI4VCIwcAKzIAtMxkI7II2 jI8vz4vEwIxGrwCI42IY6I8E87Iv6xkF7I0E14v26r1j6r4UM7AC8VAFwI0_Jr0_Gr1lb4 IE77IF4wAFIxvE14AKwVWUJVWUGwAqx4xG64xvF2IEw4CE5I8CrVC2j2Wlb7Iv0xC_CrUa nT9S1TB71UUUUUUa7-sFnT9fnUUI43ZEXa7IUeUCztUUUUUFnT9fnV15pF1DuFyrGr45Kr WUXrW5Ww43toXrpr48tFgE9FW8AF97C348tFWYya17KF9Yy3WkKrWqqrs8JrZ5XFs0yr95 Xa9xWa1kWr95Wr1UGFs2vrn7uws3AF9Fgw1ag X-detected-kernel: Linux 2.4-2.6 Subject: Re: Command extension suggestions 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, 14 Jun 2007 13:08:41 -0000 On Thu, Jun 14, 2007 at 01:50:38PM +0200, Marco Gerards wrote: > Bean writes: > > > On Thu, Jun 14, 2007 at 12:49:26PM +0200, Marco Gerards wrote: > >> Well, I see the problem but I do not agree with the solution. > >> > >> The problem for GRUB 2 is that initrd is very linux specific. It's > >> part of a loader. Perhaps we either have to extend loopback to load a > >> file into memory on beforehand. Or add a memdisk disk or so. > >> > >> One problem with initrd is that it is very architecture specific. > >> Another problem is that the initrd is unloaded when you load another > >> kernel or OS. Besides that, reusing initrd appears hackish to me :-). > > > > I have another idea on this subject. First, We can extend the function of > > grub-mkimage so that it can handle data files. The data files embed in > > core.img can be accessed using a special device such as (ed). Then, we can > > put all necessary files, such as modules, grub.cfg and other data files in > > a single core.img. This kernel is self-sustaining, no extra file is needed > > for it to function properly. > > This sounds good. In what way do you want to embed them? A > filesystem image (for example minixfs)? Some simple archive? We can embed them the same way we embed modules. Just add a header: SIGNATURE FILENAME DATA SIGNATURE is used to distinguish data file from normal module, FILENAME is used by the virtual device to identify the data. -- Bean