From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1JTl5R-0003kW-UP for garchives@archives.gentoo.org; Mon, 25 Feb 2008 21:42:14 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id ED59CE0312; Mon, 25 Feb 2008 21:42:12 +0000 (UTC) Received: from creativecommunications.com (creativecommunications.com [65.17.124.162]) by pigeon.gentoo.org (Postfix) with ESMTP id D392EE0312 for ; Mon, 25 Feb 2008 21:42:12 +0000 (UTC) Received: from [192.168.1.178] (unknown [192.168.1.178]) by creativecommunications.com (Postfix) with ESMTP id 4F79768C073 for ; Mon, 25 Feb 2008 15:42:12 -0600 (CST) Message-ID: <47C33634.1060704@gentoo.org> Date: Mon, 25 Feb 2008 15:42:12 -0600 From: Andrew Gaffney User-Agent: Thunderbird 2.0.0.9 (X11/20071228) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-catalyst@lists.gentoo.org Reply-to: gentoo-catalyst@lists.gentoo.org MIME-Version: 1.0 To: gentoo-catalyst@lists.gentoo.org Subject: Re: [gentoo-catalyst] Catalyst 2.0.6_pre9 mksquashfs hangs building squashfs + solution References: <1203975170.10423.8.camel@localhost> In-Reply-To: <1203975170.10423.8.camel@localhost> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: b865798a-d6b1-44f2-a375-73d0c340e12e X-Archives-Hash: 52d4397d13fd4e1e890d71546469a7c8 Pongracz Istvan wrote: > Hi, > > This evening I run into a problem, when I built my custom livecd. > It contains an installed and configured postgresql and one of its file > had something, which caused to mksquashfs hanged up. > > So, after I append the -info (mksquashfs argument), I caught a file, > which caused the problem several times. > > After asking my old spanish friend (Manual) and google, I used the > -no-sparse argument to avoid hanging mksquashfs. > > After it I succeed to create the image. > > I am not sure, but it seems, it is safe to use the -no-sparse argument > to avoid some problems. > Just my experience. Are you sure it was hung? Was it just trying to squash a very "large" sparse file? Can you give us the URL that gave you the idea to use -no-sparse? -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- gentoo-catalyst@lists.gentoo.org mailing list