Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 7 Feb 2002 05:02:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 7 Feb 2002 05:01:52 -0500 Received: from borderworlds.dk ([193.162.142.101]:18184 "HELO klingon.borderworlds.dk") by vger.kernel.org with SMTP id ; Thu, 7 Feb 2002 05:01:37 -0500 To: linux-kernel@vger.kernel.org Subject: Re: Problems with iso9660 as initrd In-Reply-To: From: Christian Laursen Date: 07 Feb 2002 11:01:33 +0100 In-Reply-To: Message-ID: Lines: 22 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org "H. Peter Anvin" writes: > Followup to: > By author: Christian Laursen > In newsgroup: linux.dev.kernel > > > > > > Also, you don't have CONFIG_ZISOFS set... > > > > Sorry for not being precise enough. It is not a zisofs, just compressed > > with gzip as usual for an initrd image. > > > > Still unusual, though. Why iso9660? It's not particularly well > suited for an initrd, especially because of all the redundant data > structures and extra blocking. Mostly because it is easily scriptable to build it with tools usually available. -- Best regards Christian Laursen - 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/