Phillip Lougher <[EMAIL PROTECTED]> wrote: > > [ on-disk bitfields ] > > I've checked compatibilty against Intel 32 and 64 bit architectures, > PPC 32/64 bit, ARM, MIPS > and SPARC. I've used compilers from 2.91.x upto 3.4...
hm, OK. I remain a bit skeptical but it sounds like you're the expert. I guess if things later explode it will be pretty obvious, and the filesystem will need rework. One thing which I assume we don't know at this stage is whether all 27 architectures work as expected - you can bet ia64 does it differently ;) How does one test that? Create a filesystem-in-a-file via mksquashfs, then transfer that to a different box, then try and mount and use it, I assume? When you upissue these patches, please include in the changelog pointers to the relevant userspace support tools - mksquashfs, fsck.squashfs, etc. I guess http://squashfs.sourceforge.net/ will suit. Also, this filesystem seems to do the same thing as cramfs. We'd need to understand in some detail what advantages squashfs has over cramfs to justify merging it. Again, that is something which is appropriate to the changelog for patch 1/1. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/