From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Drebes Subject: Re: cramfs in big endian Date: Wed, 7 Nov 2007 21:51:48 +0100 Message-ID: <200711072151.49032.lists-receive@programmierforen.de> References: <200711062216.27156.lists-receive@programmierforen.de> <4731C308.8090008@slax.org> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org To: Tomas M Return-path: Received: from server001.webpack.hosteurope.de ([80.237.130.9]:37441 "EHLO server001.webpack.hosteurope.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753964AbXKGUwL (ORCPT ); Wed, 7 Nov 2007 15:52:11 -0500 In-Reply-To: <4731C308.8090008@slax.org> Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Hi! > I would suggest you to use squashfs instead of cramfs. > First, it's newer, it's better, it's actively developed, it doesn't have any > limits like the bad cramfs. I'm developing a new linux based firmware for my router which uses cramfs. Switching to squashfs still needs some time. Meanwhile, I have to work with cramfs. As the router uses the big endian format and as my machine works with the little endian format, I'm unable to mount the router's filesystem images. Andi