linux-kernel - Re: Initrd and ramdisk support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.61.0609291008170.20243@yvahk01.tjqt.qr>
Date:	Fri, 29 Sep 2006 10:10:59 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Stephan Wiebusch <stephanwib@...nline.de>
cc:	linux-kernel@...r.kernel.org
Subject: 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 majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/