Re: Initrd and ramdisk support

>Unpacking initramfs...<0>Kernel panic - not syncing: bad gzip magic numbers
>Unpacking initramfs...<0>Kernel panic - not syncing: no cpio magic
>
>i luckily was able to determine the malefactor. There was the initrd support 
>built into the kernel while the ramdisk driver was just built as a module.
>
>Is it senseful to have the possibility to built the Initramfs/Initrd-support 
>without having the ramdisk driver forced to be integrated also?

I hardly see a point in using initrd support without ramdisk. Where would you
store the initrd on instead?


Jan Engelhardt
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: Initrd and ramdisk support
    • From: Michael Tokarev <[email protected]>

• References:
  • Initrd and ramdisk support
    • From: Stephan Wiebusch <[email protected]>

• Prev by Date: Re: GPLv3 Position Statement
• Next by Date: Re: [PATCH] Don't leak 'old_class_name' in drivers/base/core.c::device_rename()
• Previous by thread: Initrd and ramdisk support
• Next by thread: Re: Initrd and ramdisk support
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]