636 lines
21 KiB
HTML
636 lines
21 KiB
HTML
|
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
|
<HTML><HEAD><TITLE>Man page of NTFS-3G</TITLE>
|
|
</HEAD><BODY>
|
|
<H1>NTFS-3G</H1>
|
|
Section: Maintenance Commands (8)<BR>Updated: Mar 2014<BR><A HREF="#index">Index</A>
|
|
<A HREF="/cgi-bin/man/man2html">Return to Main Contents</A><HR>
|
|
|
|
<A NAME="lbAB"> </A>
|
|
<H2>NAME</H2>
|
|
|
|
ntfs-3g - Third Generation Read/Write NTFS Driver
|
|
<A NAME="lbAC"> </A>
|
|
<H2>SYNOPSIS</H2>
|
|
|
|
<B>ntfs-3g</B>
|
|
|
|
<B>[-o </B><I>option</I><B>[,...]]</B>
|
|
<I>volume mount_point</I>
|
|
|
|
<BR>
|
|
|
|
<B>mount -t ntfs-3g</B>
|
|
|
|
<B>[-o </B><I>option</I><B>[,...]]</B>
|
|
<I>volume mount_point</I>
|
|
|
|
<BR>
|
|
|
|
<B>lowntfs-3g</B>
|
|
|
|
<B>[-o </B><I>option</I><B>[,...]]</B>
|
|
<I>volume mount_point</I>
|
|
|
|
<BR>
|
|
|
|
<B>mount -t lowntfs-3g</B>
|
|
|
|
<B>[-o </B><I>option</I><B>[,...]]</B>
|
|
<I>volume mount_point</I>
|
|
|
|
<A NAME="lbAD"> </A>
|
|
<H2>DESCRIPTION</H2>
|
|
|
|
<B>ntfs-3g</B> is an NTFS driver, which can create, remove, rename, move
|
|
files, directories, hard links, and streams; it can read and write files,
|
|
including streams, sparse files and transparently compressed files; it can
|
|
handle special files like symbolic links, devices, and FIFOs; moreover it
|
|
provides standard management of file ownership and permissions, including
|
|
POSIX ACLs.
|
|
<P>
|
|
|
|
It comes in two variants <B>ntfs-3g</B> and <B>lowntfs-3g</B> with
|
|
a few differences mentioned below in relevant options descriptions.
|
|
<P>
|
|
|
|
The <I>volume</I> to be mounted can be either a block device or
|
|
an image file.
|
|
<A NAME="lbAE"> </A>
|
|
<H3>Windows hibernation and fast restarting</H3>
|
|
|
|
On computers which can be dual-booted into Windows or Linux, Windows has
|
|
to be fully shut down before booting into Linux, otherwise the NTFS file
|
|
systems on internal disks may be left in an inconsistent state and changes
|
|
made by Linux may be ignored by Windows.
|
|
<P>
|
|
|
|
So, Windows may not be left in hibernation when starting Linux, in order
|
|
to avoid inconsistencies. Moreover, the fast restart feature available on
|
|
recent Windows systems has to be disabled. This can be achieved by issuing
|
|
as an Administrator the Windows command which disables both
|
|
hibernation and fast restarting :
|
|
<DL COMPACT><DT id="1"><DD>
|
|
<P>
|
|
powercfg /h off
|
|
<P>
|
|
</DL>
|
|
|
|
If either Windows is hibernated or its fast restart is enabled, partitions
|
|
on internal disks are forced to be mounted in read-only mode.
|
|
<A NAME="lbAF"> </A>
|
|
<H3>Access Handling and Security</H3>
|
|
|
|
By default, files and directories are owned by the effective
|
|
user and group of the mounting process, and everybody has
|
|
full read, write, execution and directory browsing permissions.
|
|
You can also assign permissions to a single user by using the
|
|
<B>uid</B>
|
|
|
|
and/or the
|
|
<B>gid </B>
|
|
|
|
options together with the
|
|
<B>umask,</B>
|
|
|
|
or
|
|
<B>fmask</B>
|
|
|
|
and
|
|
<B>dmask</B>
|
|
|
|
options.
|
|
<P>
|
|
|
|
Doing so, Windows users have full access to the files created by
|
|
<B>ntfs-3g.</B>
|
|
|
|
<P>
|
|
|
|
But, by setting the <B>permissions</B> option, you can benefit from the full
|
|
ownership and permissions features as defined by POSIX. Moreover, by defining
|
|
a Windows-to-Linux user mapping, the ownerships and permissions are even
|
|
applied to Windows users and conversely.
|
|
<P>
|
|
|
|
If
|
|
<B>ntfs-3g </B>
|
|
|
|
is set setuid-root then non-root users will
|
|
be also able to mount volumes.
|
|
<A NAME="lbAG"> </A>
|
|
<H3>Windows Filename Compatibility</H3>
|
|
|
|
NTFS supports several filename namespaces: DOS, Win32 and POSIX. While the
|
|
<B>ntfs-3g</B> driver handles all of them, it always creates new files in the
|
|
POSIX namespace for maximum portability and interoperability reasons.
|
|
This means that filenames are case sensitive and all characters are
|
|
allowed except '/' and '\0'. This is perfectly legal on Windows, though
|
|
some application may get confused. The option <B>windows_names</B> may be
|
|
used to apply Windows restrictions to new file names.
|
|
<A NAME="lbAH"> </A>
|
|
<H3>Alternate Data Streams (ADS)</H3>
|
|
|
|
NTFS stores all data in streams. Every file has exactly one unnamed
|
|
data stream and can have many named data streams. The size of a file is the
|
|
size of its unnamed data stream. By default, <B>ntfs-3g</B> will only read
|
|
the unnamed data stream.
|
|
<P>
|
|
|
|
By using the options "streams_interface=windows", with the ntfs-3g driver
|
|
(not possible with lowntfs-3g), you will be able to read any named data
|
|
streams, simply by specifying the stream's name after a colon.
|
|
For example:
|
|
<DL COMPACT><DT id="2"><DD>
|
|
<P>
|
|
cat some.mp3:artist
|
|
<P>
|
|
</DL>
|
|
|
|
Named data streams act like normal files, so you can read from them, write to
|
|
them and even delete them (using rm). You can list all the named data streams
|
|
a file has by getting the "ntfs.streams.list" extended attribute.
|
|
<A NAME="lbAI"> </A>
|
|
<H2>OPTIONS</H2>
|
|
|
|
Below is a summary of the options that <B>ntfs-3g</B> accepts.
|
|
<DL COMPACT>
|
|
<DT id="3"><B>uid=</B><I>value</I> and <B>gid=</B><I>value</I><DD>
|
|
Set the owner and the group of files and directories. The values are numerical.
|
|
The defaults are the uid and gid of the current process.
|
|
<DT id="4"><B>umask=</B><I>value</I>
|
|
|
|
<DD>
|
|
Set the bitmask of the file and directory permissions that are not
|
|
present. The value is given in octal. The default value is 0 which
|
|
means full access to everybody.
|
|
<DT id="5"><B>fmask=</B><I>value</I>
|
|
|
|
<DD>
|
|
Set the bitmask of the file permissions that are not present.
|
|
The value is given in octal. The default value is 0 which
|
|
means full access to everybody.
|
|
<DT id="6"><B>dmask=</B><I>value</I>
|
|
|
|
<DD>
|
|
Set the bitmask of the directory permissions that are not
|
|
present. The value is given in octal. The default value is 0 which
|
|
means full access to everybody.
|
|
<DT id="7"><B>usermapping=</B><I>file-name</I>
|
|
|
|
<DD>
|
|
Use file <I>file-name</I> as the user mapping file instead of the default
|
|
<B>.NTFS-3G/UserMapping</B>. If <I>file-name</I> defines a full path, the
|
|
file must be located on a partition previously mounted. If it defines a
|
|
relative path, it is interpreted relative to the root of NTFS partition
|
|
being mounted.
|
|
</DL>
|
|
<P>
|
|
|
|
<DL COMPACT><DT id="8"><DD>
|
|
When a user mapping file is defined, the options <B>uid=</B>, <B>gid=</B>,
|
|
<B>umask=</B>, <B>fmask=</B>, <B>dmask=</B> and <B>silent</B> are ignored.
|
|
</DL>
|
|
|
|
<DL COMPACT>
|
|
<DT id="9"><B>permissions</B>
|
|
|
|
<DD>
|
|
Set standard permissions on created files and use standard access control.
|
|
This option is set by default when a user mapping file is present.
|
|
<DT id="10"><B>acl</B>
|
|
|
|
<DD>
|
|
Enable setting Posix ACLs on created files and use them for access control.
|
|
This option is only available on specific builds. It is set by default
|
|
when a user mapping file is present and the
|
|
<B>permissions</B>
|
|
|
|
mount option is not set.
|
|
<DT id="11"><B>inherit</B>
|
|
|
|
<DD>
|
|
When creating a new file, set its initial protections
|
|
according to inheritance rules defined in parent directory. These rules
|
|
deviate from Posix specifications, but yield a better Windows
|
|
compatibility. The <B>permissions</B> option or a valid user mapping file
|
|
is required for this option to be effective.
|
|
<DT id="12"><B>ro</B>
|
|
|
|
<DD>
|
|
Mount filesystem read-only. Useful if Windows is hibernated or the
|
|
NTFS journal file is unclean.
|
|
<DT id="13"><B>locale=</B><I>value</I>
|
|
|
|
<DD>
|
|
This option can be useful when wanting a language specific locale environment.
|
|
It is however discouraged as it leads to files with untranslatable chars
|
|
to not be visible.
|
|
<DT id="14"><B>force</B>
|
|
|
|
<DD>
|
|
This option is obsolete. It has been superseded by the <B>recover</B> and
|
|
<B>norecover</B> options.
|
|
<DT id="15"><B>recover</B>
|
|
|
|
<DD>
|
|
Recover and try to mount a partition which was not unmounted properly by
|
|
Windows. The Windows logfile is cleared, which may cause inconsistencies.
|
|
Currently this is the default option.
|
|
<DT id="16"><B>norecover</B>
|
|
|
|
<DD>
|
|
Do not try to mount a partition which was not unmounted properly by Windows.
|
|
<DT id="17"><B>ignore_case </B>(only with lowntfs-3g)
|
|
|
|
<DD>
|
|
Ignore character case when accessing a file (<B>FOO</B>, <B>Foo</B>, <B>foo</B>,
|
|
etc. designate the same file). All files are displayed with lower case in
|
|
directory listings.
|
|
<DT id="18"><B>remove_hiberfile</B>
|
|
|
|
<DD>
|
|
When the NTFS volume is hibernated, a read-write mount is denied and
|
|
a read-only mount is forced. One needs either to resume Windows and
|
|
shutdown it properly, or use this option which will remove the Windows
|
|
hibernation file. Please note, this means that the saved Windows
|
|
session will be completely lost. Use this option under your own
|
|
responsibility.
|
|
<DT id="19"><B>atime, noatime, relatime</B>
|
|
|
|
<DD>
|
|
The
|
|
<B>atime </B>
|
|
|
|
option updates inode access time for each access.
|
|
<P>
|
|
The
|
|
<B>noatime </B>
|
|
|
|
option disables inode access time updates which can speed up
|
|
file operations and prevent sleeping (notebook) disks spinning
|
|
up too often thus saving energy and disk lifetime.
|
|
<P>
|
|
The
|
|
<B>relatime </B>
|
|
|
|
option is very similar to
|
|
<B>noatime. </B>
|
|
|
|
It updates inode access times relative to modify or change time.
|
|
The access time is only updated if the previous access time was earlier
|
|
than the current modify or change time. Unlike
|
|
<B>noatime</B>
|
|
|
|
this option doesn't break applications that need to know
|
|
if a file has been read since the last time it was modified.
|
|
This is the default behaviour.
|
|
<DT id="20"><B>delay_mtime[= value]</B>
|
|
|
|
<DD>
|
|
Only update the file modification time and the file change time of a file
|
|
when it is closed or when the indicated delay since the previous update has
|
|
elapsed. The argument is a number of seconds, with a default value of 60.
|
|
This is mainly useful for big files which are kept open for a long
|
|
time and written to without changing their size, such as databases or file
|
|
system images mounted as loop.
|
|
<DT id="21"><B>show_sys_files</B>
|
|
|
|
<DD>
|
|
Show the metafiles in directory listings. Otherwise the default behaviour is
|
|
to hide the metafiles, which are special files used to store the NTFS
|
|
structure. Please note that even when this option is specified, "$MFT" may
|
|
not be visible due to a glibc bug. Furthermore, irrespectively of
|
|
show_sys_files, all files are accessible by name, for example you can always
|
|
do
|
|
"ls -l '$UpCase'".
|
|
<DT id="22"><B>hide_hid_files</B>
|
|
|
|
<DD>
|
|
Hide the hidden files and directories in directory listings, the hidden files
|
|
and directories being the ones whose NTFS attribute have the hidden flag set.
|
|
The hidden files will not be selected when using wildcards in commands,
|
|
but all files and directories remain accessible by full name, for example you
|
|
can always display the Windows trash bin directory by :
|
|
"ls -ld '$RECYCLE.BIN'".
|
|
<DT id="23"><B>hide_dot_files</B>
|
|
|
|
<DD>
|
|
Set the hidden flag in the NTFS attribute for created files and directories
|
|
whose first character of the name is a dot. Such files and directories
|
|
normally do not appear in directory listings, and when the flag is set
|
|
they do not appear in Windows directory displays either.
|
|
When a file is renamed or linked with a new name, the hidden flag is
|
|
adjusted to the latest name.
|
|
<DT id="24"><B>windows_names</B>
|
|
|
|
<DD>
|
|
This option prevents files, directories and extended attributes to be
|
|
created with a name not allowed by windows, because
|
|
<DL COMPACT><DT id="25"><DD>
|
|
<DL COMPACT><DT id="26"><DD>
|
|
<P>
|
|
- it contains some not allowed character,
|
|
<BR>
|
|
|
|
- or the last character is a space or a dot,
|
|
<BR>
|
|
|
|
- or the name is reserved.
|
|
<P>
|
|
</DL>
|
|
|
|
The forbidden characters are the nine characters " * / : < > ? \ | and
|
|
those whose code is less than 0x20, and
|
|
the reserved names are CON, PRN, AUX, NUL, COM1..COM9, LPT1..LPT9,
|
|
with no suffix or followed by a dot.
|
|
<P>
|
|
Existing such files can still be read (and renamed).
|
|
</DL>
|
|
|
|
<DT id="27"><B>allow_other</B>
|
|
|
|
<DD>
|
|
This option overrides the security measure restricting file access
|
|
to the user mounting the filesystem. This option is only
|
|
allowed to root, but this restriction can be overridden by
|
|
the 'user_allow_other' option in the /etc/fuse.conf file.
|
|
<DT id="28"><B>max_read=</B><I>value</I>
|
|
|
|
<DD>
|
|
With this option the maximum size of read operations can be set.
|
|
The default is infinite. Note that the size of read requests is
|
|
limited anyway to 32 pages (which is 128kbyte on i386).
|
|
<DT id="29"><B>silent</B>
|
|
|
|
<DD>
|
|
Do nothing, without returning any error, on chmod and chown operations
|
|
and on permission checking errors,
|
|
when the <B>permissions</B> option is not set and no user mapping file
|
|
is defined. This option is on by default, and when set off (through option
|
|
<B>no_def_opts</B>) ownership and permissions parameters have to be set.
|
|
<DT id="30"><B>no_def_opts</B>
|
|
|
|
<DD>
|
|
By default ntfs-3g acts as if "silent" (ignore permission errors when
|
|
permissions are not enabled),
|
|
"allow_other" (allow any user to access files) and "nonempty"
|
|
(allow mounting on non-empty directories) were set, and "no_def_opts"
|
|
cancels these default options.
|
|
<DT id="31"><B>streams_interface=</B><I>value</I>
|
|
|
|
<DD>
|
|
This option controls how the user can access Alternate Data Streams (ADS) or
|
|
in other words, named data streams. It can be set to, one of <B>none</B>,
|
|
<B>windows</B> or <B>xattr</B>. If the option is set to <B>none</B>, the user
|
|
will have no access to the named data streams. If it is set to <B>windows</B>
|
|
(not possible with lowntfs-3g), then the user can access them just like in
|
|
Windows (eg. cat file:stream). If it's set to <B>xattr</B>, then the named
|
|
data streams are mapped to xattrs and user can manipulate them using
|
|
<B>{get,set}fattr</B> utilities. The default is <B>xattr</B>.
|
|
<DT id="32"><B>user_xattr</B>
|
|
|
|
<DD>
|
|
Same as <B>streams_interface=</B><I>xattr</I>.
|
|
<DT id="33"><B>efs_raw</B>
|
|
|
|
<DD>
|
|
This option should only be used in backup or restore situation.
|
|
It changes the apparent size of files and the behavior of read and
|
|
write operation so that encrypted files can be saved and restored
|
|
without being decrypted. The <B>user.ntfs.efsinfo</B> extended attribute
|
|
has also to be saved and restored for the file to be decrypted.
|
|
<DT id="34"><B>compression</B>
|
|
|
|
<DD>
|
|
This option enables creating new transparently compressed files in
|
|
directories marked for compression. A directory is marked for compression by
|
|
setting the bit 11 (value 0x00000800) in its Windows attribute. In such a
|
|
directory, new files are created compressed and new subdirectories are
|
|
themselves marked for compression. The option and the flag have no effect
|
|
on existing files. Currently this is the default option.
|
|
<DT id="35"><B>nocompression</B>
|
|
|
|
<DD>
|
|
This option disables creating new transparently compressed files in directories
|
|
marked for compression. Existing compressed files can still be read and
|
|
updated.
|
|
<DT id="36"><B>big_writes</B>
|
|
|
|
<DD>
|
|
This option prevents fuse from splitting write buffers into 4K chunks,
|
|
enabling big write buffers to be transferred from the application in a
|
|
single step (up to some system limit, generally 128K bytes).
|
|
<DT id="37"><B>debug</B>
|
|
|
|
<DD>
|
|
Makes ntfs-3g to print a lot of debug output from libntfs-3g and FUSE.
|
|
<DT id="38"><B>no_detach</B>
|
|
|
|
<DD>
|
|
Makes ntfs-3g to not detach from terminal and print some debug output.
|
|
</DL>
|
|
<A NAME="lbAJ"> </A>
|
|
<H2>USER MAPPING</H2>
|
|
|
|
NTFS uses specific ids to record the ownership of files instead of
|
|
the <B>uid</B> and <B>gid</B> used by Linux. As a consequence a mapping
|
|
between the ids has to be defined for ownerships to be recorded into
|
|
NTFS and recognized.
|
|
<P>
|
|
|
|
By default, this mapping is fetched from the file <B>.NTFS-3G/UserMapping</B>
|
|
located in the NTFS partition. The option <B>usermapping=</B> may be used
|
|
to define another location. When the option permissions is set and
|
|
no mapping file is found, a default mapping is used.
|
|
<P>
|
|
|
|
Each line in the user mapping file defines a mapping. It is organized
|
|
in three fields separated by colons. The first field identifies a <B>uid</B>,
|
|
the second field identifies a <B>gid</B> and the third one identifies the
|
|
corresponding NTFS id, known as a <B>SID</B>. The <B>uid</B> and the <B>gid</B>
|
|
are optional and defining both of them for the same <B>SID</B> is not
|
|
recommended.
|
|
<P>
|
|
|
|
If no interoperation with Windows is needed, you can use the option
|
|
<B>permissions</B> to define a standard mapping. Alternately, you may define
|
|
your own mapping by setting a single default mapping with no uid and gid. In
|
|
both cases, files created on Linux will appear to Windows as owned by a
|
|
foreign user, and files created on Windows will appear to Linux as owned by
|
|
root. Just copy the example below and replace the 9 and 10-digit numbers by
|
|
any number not greater than 4294967295. The resulting behavior is the same as
|
|
the one with the option permission set with no ownership option and no user
|
|
mapping file available.
|
|
<DL COMPACT><DT id="39"><DD>
|
|
<P>
|
|
<B>::S-1-5-21-3141592653-589793238-462643383-10000</B>
|
|
|
|
<P>
|
|
</DL>
|
|
|
|
If a strong interoperation with Windows is needed, the mapping has to be
|
|
defined for each user and group known in both system, and the <B>SID</B>s used
|
|
by Windows has to be collected. This will lead to a user mapping file like :
|
|
<DL COMPACT><DT id="40"><DD>
|
|
<P>
|
|
<B>john::S-1-5-21-3141592653-589793238-462643383-1008</B>
|
|
|
|
<B>mary::S-1-5-21-3141592653-589793238-462643383-1009</B>
|
|
|
|
<B>:smith:S-1-5-21-3141592653-589793238-462643383-513</B>
|
|
|
|
<B>::S-1-5-21-3141592653-589793238-462643383-10000</B>
|
|
|
|
<P>
|
|
</DL>
|
|
|
|
<P>
|
|
|
|
The utility <B>ntfsusermap</B> may be used to create such a user
|
|
mapping file.
|
|
<A NAME="lbAK"> </A>
|
|
<H2>EXAMPLES</H2>
|
|
|
|
Mount /dev/sda1 to /mnt/windows:
|
|
<DL COMPACT><DT id="41"><DD>
|
|
<P>
|
|
<B>ntfs-3g /dev/sda1 /mnt/windows</B>
|
|
|
|
</DL>
|
|
|
|
or
|
|
<DL COMPACT><DT id="42"><DD>
|
|
<B>mount -t ntfs-3g /dev/sda1 /mnt/windows</B>
|
|
|
|
<P>
|
|
</DL>
|
|
|
|
Mount the ntfs data partition /dev/sda3 to /mnt/data with standard Linux
|
|
permissions applied :
|
|
<DL COMPACT><DT id="43"><DD>
|
|
<P>
|
|
<B>ntfs-3g -o permissions /dev/sda3 /mnt/data</B>
|
|
|
|
</DL>
|
|
|
|
or
|
|
<DL COMPACT><DT id="44"><DD>
|
|
<B>mount -t ntfs-3g -o permissions /dev/sda3 /mnt/data</B>
|
|
|
|
<P>
|
|
</DL>
|
|
|
|
Read-only mount /dev/sda5 to /home/user/mnt and make user with uid 1000
|
|
to be the owner of all files:
|
|
<DL COMPACT><DT id="45"><DD>
|
|
<P>
|
|
<B>ntfs-3g /dev/sda5 /home/user/mnt -o ro,uid=1000</B>
|
|
|
|
<P>
|
|
</DL>
|
|
|
|
/etc/fstab entry for the above (the sixth and last field has to be zero to
|
|
avoid a file system check at boot time) :
|
|
<DL COMPACT><DT id="46"><DD>
|
|
<P>
|
|
<B>/dev/sda5 /home/user/mnt ntfs-3g ro,uid=1000 0 0</B>
|
|
|
|
<P>
|
|
</DL>
|
|
|
|
Unmount /mnt/windows:
|
|
<DL COMPACT><DT id="47"><DD>
|
|
<P>
|
|
<B>umount /mnt/windows</B>
|
|
|
|
<P>
|
|
</DL>
|
|
|
|
<A NAME="lbAL"> </A>
|
|
<H2>EXIT CODES</H2>
|
|
|
|
To facilitate the use of the
|
|
<B>ntfs-3g</B>
|
|
|
|
driver in scripts, an exit code is returned to give an indication of the
|
|
mountability status of a volume. Value 0 means success, and all other
|
|
ones mean an error. The unique error codes are documented in the
|
|
<B><A HREF="/cgi-bin/man/man2html?8+ntfs-3g.probe">ntfs-3g.probe</A></B>(8)
|
|
|
|
manual page.
|
|
<A NAME="lbAM"> </A>
|
|
<H2>KNOWN ISSUES</H2>
|
|
|
|
Please see
|
|
<DL COMPACT><DT id="48"><DD>
|
|
<P>
|
|
<A HREF="http://www.tuxera.com/support/">http://www.tuxera.com/support/</A>
|
|
<P>
|
|
</DL>
|
|
|
|
for common questions and known issues.
|
|
If you would find a new one in the latest release of
|
|
the software then please send an email describing it
|
|
in detail. You can contact the
|
|
development team on the <A HREF="mailto:ntfs-3g-devel@lists.sf.net">ntfs-3g-devel@lists.sf.net</A>
|
|
address.
|
|
<A NAME="lbAN"> </A>
|
|
<H2>AUTHORS</H2>
|
|
|
|
<B>ntfs-3g </B>
|
|
|
|
was based on and a major improvement to ntfsmount and libntfs which were
|
|
written by Yura Pakhuchiy and the Linux-NTFS team. The improvements were
|
|
made, the ntfs-3g project was initiated and currently led by long time
|
|
Linux-NTFS team developer Szabolcs Szakacsits (<A HREF="mailto:szaka@tuxera.com">szaka@tuxera.com</A>).
|
|
<A NAME="lbAO"> </A>
|
|
<H2>THANKS</H2>
|
|
|
|
Several people made heroic efforts, often over five or more
|
|
years which resulted the ntfs-3g driver. Most importantly they are
|
|
Anton Altaparmakov, Jean-Pierre André, Richard Russon, Szabolcs Szakacsits,
|
|
Yura Pakhuchiy, Yuval Fledel, and the author of the groundbreaking FUSE
|
|
filesystem development framework, Miklos Szeredi.
|
|
<A NAME="lbAP"> </A>
|
|
<H2>SEE ALSO</H2>
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?8+ntfs-3g.probe">ntfs-3g.probe</A></B>(8),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?8+ntfsprogs">ntfsprogs</A></B>(8),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?5+attr">attr</A></B>(5),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+getfattr">getfattr</A></B>(1)
|
|
|
|
<P>
|
|
|
|
<HR>
|
|
<A NAME="index"> </A><H2>Index</H2>
|
|
<DL>
|
|
<DT id="49"><A HREF="#lbAB">NAME</A><DD>
|
|
<DT id="50"><A HREF="#lbAC">SYNOPSIS</A><DD>
|
|
<DT id="51"><A HREF="#lbAD">DESCRIPTION</A><DD>
|
|
<DL>
|
|
<DT id="52"><A HREF="#lbAE">Windows hibernation and fast restarting</A><DD>
|
|
<DT id="53"><A HREF="#lbAF">Access Handling and Security</A><DD>
|
|
<DT id="54"><A HREF="#lbAG">Windows Filename Compatibility</A><DD>
|
|
<DT id="55"><A HREF="#lbAH">Alternate Data Streams (ADS)</A><DD>
|
|
</DL>
|
|
<DT id="56"><A HREF="#lbAI">OPTIONS</A><DD>
|
|
<DT id="57"><A HREF="#lbAJ">USER MAPPING</A><DD>
|
|
<DT id="58"><A HREF="#lbAK">EXAMPLES</A><DD>
|
|
<DT id="59"><A HREF="#lbAL">EXIT CODES</A><DD>
|
|
<DT id="60"><A HREF="#lbAM">KNOWN ISSUES</A><DD>
|
|
<DT id="61"><A HREF="#lbAN">AUTHORS</A><DD>
|
|
<DT id="62"><A HREF="#lbAO">THANKS</A><DD>
|
|
<DT id="63"><A HREF="#lbAP">SEE ALSO</A><DD>
|
|
</DL>
|
|
<HR>
|
|
This document was created by
|
|
<A HREF="/cgi-bin/man/man2html">man2html</A>,
|
|
using the manual pages.<BR>
|
|
Time: 00:06:14 GMT, March 31, 2021
|
|
</BODY>
|
|
</HTML>
|