public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: hpa@zytor.com (H. Peter Anvin)
To: linux-kernel@vger.kernel.org
Subject: Re: BOOT_CS
Date: Tue, 24 Feb 2004 15:39:51 +0000 (UTC)	[thread overview]
Message-ID: <c1fr87$r2a$1@terminus.zytor.com> (raw)
In-Reply-To: 20040224100530.68794.qmail@web11805.mail.yahoo.com

Followup to:  <20040224100530.68794.qmail@web11805.mail.yahoo.com>
By author:    =?iso-8859-1?q?Etienne=20Lorrain?= <etienne_lorrain@yahoo.fr>
In newsgroup: linux.dev.kernel
> 
>   The other problem is for the people who want to check the validity
>  of the RAM disk before starting Linux - for instance by checking
>  the CRC32 of the decompressed RAM disk - and stop the boot process
>  before it is too late - i.e. in the bootloader when you can select
>  another kernel version / initrd to load.
>   You cannot place the decompressed initrd at a maximum address before
>  knowing its decompressed size - the address to place it is the max
>  address (or the end of free RAM) minus ramdisk size if I remember
>  correctly. That is working for so long loading the decompressed
>  initrd after few Mb after the last kernel byte (so that the kernel
>  will move it where it wants - no need to move it twice) that I do
>  not remember the details. Did you changed this part?
> 

If you absolutely want to do this -- for pretty much no reason -- you
can either decompress it twice, decompress it to nowhere (after all,
the kernel will decompress it when it starts) or move it into place
before starting the kernel.

	-hpa

  reply	other threads:[~2004-02-24 15:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-24 10:05 BOOT_CS Etienne Lorrain
2004-02-24 15:39 ` H. Peter Anvin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-26 12:17 BOOT_CS Etienne Lorrain
2004-02-26 21:49 ` BOOT_CS Denis Vlasenko
2004-02-27 10:03   ` BOOT_CS Etienne Lorrain
2004-02-27 18:41 ` BOOT_CS H. Peter Anvin
2004-02-25 10:30 BOOT_CS Etienne Lorrain
2004-02-25 16:23 ` BOOT_CS H. Peter Anvin
2004-02-21  5:47 BOOT_CS H. Peter Anvin
2004-02-21 12:43 ` BOOT_CS Coywolf Qi Hunt
2004-02-21 16:32   ` BOOT_CS Jamie Lokier
2004-02-22 15:13 ` BOOT_CS Eric W. Biederman
2004-02-22 19:47   ` BOOT_CS H. Peter Anvin
2004-02-22 22:05     ` BOOT_CS Eric W. Biederman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='c1fr87$r2a$1@terminus.zytor.com' \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox