From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomas M Subject: Re: cramfs in big endian Date: Wed, 07 Nov 2007 14:52:08 +0100 Message-ID: <4731C308.8090008@slax.org> References: <200711062216.27156.lists-receive@programmierforen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org To: Andi Drebes Return-path: Received: from ns1.bluetone.cz ([212.158.128.13]:58653 "EHLO ns1.bluetone.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758604AbXKGOjA (ORCPT ); Wed, 7 Nov 2007 09:39:00 -0500 In-Reply-To: <200711062216.27156.lists-receive@programmierforen.de> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org > I'm currently trying to enable the cramfs to mount filesystems with a > different endianness. 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. Moreover, it currently supports both endians. (hurry up, as kernel people said in the past that squashfs should NEVER EVER support multiple endians, so the feature will be dropped from squashfs, in order to get it into mainline kernel more easily; if my informations are correct). Tomas M