Re: cramfs problems, also file(1)
On Mon, 16 Jul 2001 20:27, David Schleef wrote:
> On Mon, Jul 16, 2001 at 02:03:57PM +0200, Russell Coker wrote:
> > Also I have just submitted a wishlist bug against the file package to
> > have the following added to the magic list. Did I get it right for big
> > endian?
> >
> > # cramfs filesystem
> > 0 long 0x28cd3d45 Linux Compressed ROM File System, little
> > endian 0 long 0x453dcd28 Linux Compressed ROM File System,
> > big endian
>
> According to Linus, big endian cramfs doesn't exist. But then,
> since people are using big endian cramfs, and he hasn't accepted
> my (or anyone else's) patches for LE cramfs on BE hosts, it's
> likely to stay. A warning might be in order, though.
Is it possible for a cramfs image to have data that isn't endian specific?
I expect that as the usual contents for cramfs is kernel modules they are
inherantly CPU (and therefore endian) specific and therefore there is no
point in trying to achieve portability. Or am I missing something?
I know the docs make some vague reference to CDs, but I couldn't imagine
anyone wanting to use cramfs instead of iso9660 or Ext2 for CDs (I use Ext2
for most of my CDs).
--
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
http://www.coker.com.au/projects.html Projects I am working on
http://www.coker.com.au/~russell/ My home page
Reply to: