> I'm inclined to mark loopback DANGEROUS because there apparently still
> isn't a maintainer for it. And the next person who suggests using it
> instead of a real filesystem (ramfs, cramfs, JFFS) should be forced to
> actually make it work right first!
Several folks have tried fixing it. The idea of replacing it with a raid
layer equivalent was also kicked around at UKUUG and other places. The theory
being that loopback is better done as a block remapping algorithm at the block
layer, thus killing the double caching problem, sorting out the lack of read
ahead and more
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jul 31 2000 - 21:00:35 EST