Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750735AbWI2IL4 (ORCPT ); Fri, 29 Sep 2006 04:11:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751640AbWI2IL4 (ORCPT ); Fri, 29 Sep 2006 04:11:56 -0400 Received: from emailer.gwdg.de ([134.76.10.24]:8877 "EHLO emailer.gwdg.de") by vger.kernel.org with ESMTP id S1750735AbWI2ILy (ORCPT ); Fri, 29 Sep 2006 04:11:54 -0400 Date: Fri, 29 Sep 2006 10:10:59 +0200 (MEST) From: Jan Engelhardt To: Stephan Wiebusch cc: linux-kernel@vger.kernel.org Subject: Re: Initrd and ramdisk support In-Reply-To: <200609282147.41671.stephanwib@t-online.de> Message-ID: References: <200609282147.41671.stephanwib@t-online.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Report: Content analysis: 0.0 points, 6.0 required _SUMMARY_ Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 822 Lines: 21 >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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/