Re: [PATCH][2/2] SquashFS

[Phillip Lougher]

Pavel Machek wrote:

> Well, out-of-tree maintainenance takes lot of time, too, so by keeping
> limited code out-of-kernel we provide quite good incentive to make
> those limits go away.

Sorry but I'm not calling Squashfs "limited" and I don't think it is. 
If you wanted to nit-pick many of the current filesystems in the kernel 
have various "limitations".

Your comment about not wanting more than one compressed filesystem in 
the kernel is groundless.  There's lots of _uncompressed_ filesystems in 
the kernel, why do we need them all?  Let's just pick one and throw the 
rest away?  Hmmm?  Anyway there's already three compressed filesystems 
in the kernel, each doing various specialised tasks: jffs2, zisofs, and 
cramfs.  No objections were raised then, why now?

As for your comment about "proving good incentive to make those limits 
go away", in many cases it's more likely to make people give up and walk 
away from any further kernel work.


> Perhaps squashfs is good enough improvement over cramfs... But I'd
> like those 4Gb limits to go away.

So would I.  But it is a totally groundless reason to refuse kernel 
submission because of that, Squashfs users are quite happily using it 
with such a "terrible" limitation.  I'm asking for Squashfs to be put in 
the kernel _now_ because users are asking me to do it _now_.  If it 
doesn't go in, then they'll want to know why the kernel clique has 
become so unreceptive to new pieces of work which they consider a key 
piece of their Linux 'experience', and for that matter so would I.

Phillip
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/