Rick Byers wrote:
> > It propably reads/writes NTFS5, but doesn't make use of the additional
> > NTFS5 features I mentionned above. This is the same what WinNT makes
> > with NTFS5. It is able to handle NTFS5 (in terms of reading and
> > writing), but doesn't use the additional functionalities of NTFS5.
> 
> That makes sense... A quick grep of the source comes up emtpy for
> "encrypt" or "journal".

The compression should be supported, in that it should be possible
to read the file contents correctly. Journalling support
is not really useful now, since we don't support changes to NTFS
filesystems for this to be needed. Even after the write support
would be better, it would be tough to get the journalling work
right. The structure of the NTFS filesystem journal is not documented
AFAIK.

As Christos said already, the write support is not really useful
at this point. Since it's not used, it's not tested well and
thus potentially dangerous to use. Don't use it, it's better
to mount NTFS read-only at this moment.

I've updated the mount_ntfs(8) manpage on -current to note
the offset 63 thing. Good spot, Christos :)

Jaromir
-- 
Jaromir Dolecek <jdolecek@NetBSD.org> http://www.NetBSD.org/Ports/i386/ps2.html
-=  Those who would give up liberty for a little temporary safety deserve  =-
-=  neither liberty nor safety, and will lose both.  -- Benjamin Franklin  =-