From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1HymnA-0005wK-OV for mharc-grub-devel@gnu.org; Thu, 14 Jun 2007 06:43:04 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Hymn9-0005vo-A1 for grub-devel@gnu.org; Thu, 14 Jun 2007 06:43:03 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Hymn8-0005vV-OW for grub-devel@gnu.org; Thu, 14 Jun 2007 06:43:02 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Hymn8-0005vP-BL for grub-devel@gnu.org; Thu, 14 Jun 2007 06:43:02 -0400 Received: from smtp-vbr2.xs4all.nl ([194.109.24.22]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Hymn7-0001TC-Os for grub-devel@gnu.org; Thu, 14 Jun 2007 06:43:02 -0400 Received: from localhost.localdomain (249-174.surfsnel.dsl.internl.net [145.99.174.249]) by smtp-vbr2.xs4all.nl (8.13.8/8.13.8) with ESMTP id l5EAh0lB034860 for ; Thu, 14 Jun 2007 12:43:00 +0200 (CEST) (envelope-from mgerards@xs4all.nl) From: Marco Gerards To: The development of GRUB 2 References: <20070614034649.GA591@ws3.vdp.com> <20070614060809.GA27145@aragorn> <20070614062451.GA591@ws3.vdp.com> <871wgex473.fsf@xs4all.nl> <20070614102419.GA633@ws3.vdp.com> Mail-Copies-To: mgerards@xs4all.nl Date: Thu, 14 Jun 2007 12:49:26 +0200 In-Reply-To: <20070614102419.GA633@ws3.vdp.com> (bean123@126.com's message of "Thu, 14 Jun 2007 18:24:19 +0800") Message-ID: <87sl8uvmix.fsf@xs4all.nl> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by XS4ALL Virus Scanner X-detected-kernel: FreeBSD 4.6-4.9 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 10:43:03 -0000 Bean writes: > On Thu, Jun 14, 2007 at 11:42:24AM +0200, Marco Gerards wrote: >> Bean writes: >> >> [...] >> >> >> That sounds much cleaner IMHO. But IIRC (md) is already in use by the >> >> RAID/LVM stuff ? >> >> >> > >> > Maybe (mem) ? >> >> When would this be useful? > > You can use it to dump physical memory, for example, > > od (mem)+2 > > dump first 1K of memory > > od --skip-bytes=0x413 --read-bytes=2 (mem) > > dump the word at 0x413. > > I can't think of other use at the moment. Right, so mainly debugging :) >> > Also, I don't know if GRUB2 kernel support initrd. You can start grub4dos >> > like this: >> > >> > kernel /grub.exe >> > initrd /aa.img >> > >> > Inside grub4dos, the initrd can be access using (rd). It would be nice if >> > grub2 support this kind of usage. >> >> You can use the loopback command to do this, if you want to access a >> filesystem image. >> >> loopback (loop) /foo/bar.img >> ls -l (loop)/ > > Initrd can still be useful. In some case, it's not easy to access the boot > media, such as, cdrom or pxe. To boot from such media, you can either put > everything in core.img, or you can create a minimum core.img, and put other > files, like *.mod, grub.cfg, font, etc, in an initrd. The initrd can be > loaded along with core.img, using loader such as isolinux or pxelinux. 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 :-). -- Marco