From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1JI0MS-0008PQ-TQ for mharc-grub-devel@gnu.org; Thu, 24 Jan 2008 06:35:12 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JI0MR-0008P7-64 for grub-devel@gnu.org; Thu, 24 Jan 2008 06:35:11 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JI0MP-0008OI-Ec for grub-devel@gnu.org; Thu, 24 Jan 2008 06:35:10 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JI0MP-0008OB-0w for grub-devel@gnu.org; Thu, 24 Jan 2008 06:35:09 -0500 Received: from aybabtu.com ([69.60.117.155]) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JI0MO-0002ym-HV for grub-devel@gnu.org; Thu, 24 Jan 2008 06:35:08 -0500 Received: from [192.168.10.6] (helo=thorin) by aybabtu.com with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1JI0MF-0007IR-1Z for grub-devel@gnu.org; Thu, 24 Jan 2008 12:35:02 +0100 Received: from rmh by thorin with local (Exim 4.63) (envelope-from ) id 1JI0K4-0000eS-Nh for grub-devel@gnu.org; Thu, 24 Jan 2008 12:32:44 +0100 Date: Thu, 24 Jan 2008 12:32:44 +0100 From: Robert Millan To: The development of GRUB 2 Message-ID: <20080124113244.GA2249@thorin> References: <20080122135757.GA11484@thorin> <873asoudkm.fsf@xs4all.nl> <20080123191449.GB15742@thorin> <20080123201534.GA25534@thorin> <20080123211506.GA27338@thorin> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Organization: free as in freedom X-Message-Flag: Worried about Outlook viruses? Switch to Thunderbird! www.mozilla.com/thunderbird X-Debbugs-No-Ack: true User-Agent: Mutt/1.5.13 (2006-08-11) X-detected-kernel: by monty-python.gnu.org: Genre and OS details not recognized. Subject: Re: [PATCH] memdisk plus lnxboot extension 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, 24 Jan 2008 11:35:11 -0000 On Thu, Jan 24, 2008 at 11:40:25AM +0800, Bean wrote: > On Jan 24, 2008 5:15 AM, Robert Millan wrote: > > > > On Thu, Jan 24, 2008 at 05:04:56AM +0800, Bean wrote: > > > On Jan 24, 2008 4:15 AM, Robert Millan wrote: > > > > The region where memdisk is normally put has no size limit, only the core > > > > image itself does. Why not load it at the same address? > > > > > > I just check, the lzo decompression will overwrite the area, so we > > > can't copy initrd there. > > > > So where does your code copy it? > > currently, i don't copy it. i save the initrd address to variable > grub_memdisk_image_addr, which is then used by grub_arch_memdisk_addr > to locate the memdisk. Sorry, my question was confusing; what I meant is, where is it located when core.img is started. But Just checked in our Linux loader, and it seems to be at a very high address. However, a very high address doesn't garantee that it won't be overwritten by lzo decompression, just makes it less likely. Overall, this is why I don't like having to stick to a particular boot mechanism. If our goal is overcome the size limit in memdisk, why not design the boot mechanism ourselves? -- Robert Millan I know my rights; I want my phone call! What use is a phone call… if you are unable to speak? (as seen on /.)