Closed GoogleCodeExporter closed 8 years ago
If you *have* seen the wiki post that "somehow" "tries" to explain it, why open
a formal issue here? Even if you
wish to discuss it further, why not discuss it in the macfuse-devel forum? Why
not check out on the ntfs-3g
support forums if somebody has come up with an ntfs-specific workaround? (hint:
somebody has)
Original comment by si...@gmail.com
on 24 Sep 2007 at 7:31
Ublio is not an ntfs specific workaround but a generally usable user space i/o
caching layer to workaround kernel level OS X performance deficiencies. It's not
merged officially into ntfs-3g yet because there are reliability problems with
it and
nobody has the time to debug them. More info:
http://shadowofged.blogspot.com/2007/05/ntfs-3g-performance-gains.html
Original comment by sz...@ntfs-3g.org
on 24 Sep 2007 at 8:38
szaka: Not to split hairs about semantics, but:
* ublio is not MacFUSE-specific.
* It requires ntfs-3g source modifications (not MacFUSE source modifications).
* ntfs-3g is the only user-space file system with a block device that currently
seems to be really popular
amongst MacFUSE users.
Therefore, I'm fine calling it "ntfs-specific" (the original poster said he
didn't understand my wiki page
explanation--I don't think my calling ublio a "generally usable user-space I/O
caching workaround..." would
help explain things either.
Original comment by si...@gmail.com
on 24 Sep 2007 at 5:14
Original issue reported on code.google.com by
wolfgang...@gmail.com
on 24 Sep 2007 at 6:46