Re: BOOT_CS

From: Etienne Lorrain (etienne_lorrain_at_yahoo.fr)
Date: 02/24/04

  • Next message: Coywolf Qi Hunt: "Re: [PATCH] Remove the extra jmp"
    Date:	Tue, 24 Feb 2004 11:05:30 +0100 (CET)
    To: linux-kernel@vger.kernel.org
    
    

    > H. Peter Anvin writes:
    > > Eric W. Biederman wrote:
    > > for those folks who want to place their ramdisk as low
    > > in memory as possible?
    > The problem is that you don't know until it's too late, since it can
    > depend on dynamic factors. This is part of why your insistence of
    > putting the ramdisk in the "most incorrect" position is simply wrong.

      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?

      Etienne.

    Yahoo! Mail - Votre e-mail personnel et gratuit qui vous suit partout !
     Créez votre adresse sur http://mail.yahoo.fr
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/


  • Next message: Coywolf Qi Hunt: "Re: [PATCH] Remove the extra jmp"

    Relevant Pages

    • Re: Kernel panic: initramfs problem? [SOLVED - mostly]
      ... initrd.img-2.6.18-6-686 is 4899969 bytes in size (generic kernel) ... Following up on the initrd idea.... ... with support for the initial RAM disk enabled. ... If RAM disk support is also included, ...
      (Debian-User)
    • Minimal boot CD
      ... I knew I needed some kind of sane working environment for the kernel to ... does the initrd have to be a specific ... but it still kernel panics. ... I included RAM disk support Default RAM disk size) and ...
      (comp.os.linux.embedded)
    • [PATCH] Remove final traces of long-deprecated "ramdisk" kernel parm.
      ... Since the "ramdisk" kernel parameter has been officially deprecated ... This option instructs the kernel to set up a ramdisk of the given ... The new RAM disk also has the ability to load compressed RAM disk images, ...
      (Linux-Kernel)
    • Re: Is bin ever written to?
      ... I was thinking of putting them in a ram disk with SquashFS to speed up ... frequently accessed pages in memory anyway. ... The kernel writers usually says that it's much better to NOT use a ramdisk ...
      (Ubuntu)
    • Re: Beige PowerMac G3/266 trouble
      ... I just wanted to say that this fs is not needed to boot up the ... the ram disk, so entering /dev/ram is probably better. ... the initrd parameter gives the kernel an image with which it ...
      (comp.os.linux.powerpc)