Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Limited Write Support?' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Limited Write Support?
Authored by: kaih on Aug 04, '05 07:28:39PM

I haven't tried it personally, however the manual pages for mount_ntfs state that there is limited write support. It may just be that the automounter doesn't mount the disks read/write for safety reasons, whereas you _may_ be able to mount them read/write via the Terminal.

Here's the man page: (man mount_ntfs)

MOUNT_NTFS(8) BSD System Manager's Manual MOUNT_NTFS(8)

NAME
mount_ntfs -- mount an NTFS file system

SYNOPSIS
mount_ntfs [-a] [-s] [-u uid] [-g gid] [-m mask] special node

DESCRIPTION
The mount_ntfs utility attaches the NTFS file system residing on the
device special to the global file system namespace at the location indi-
cated by node. This command is normally executed by mount(8) at boot
time, but can be used by any user to mount an NTFS file system on any
directory that they own (provided, of course, that they have appropriate
access to the device that contains the file system).

The options are as follows:

-a Force behaviour to return MS-DOS 8.3 names also on readdir().

-s Make name lookup case sensitive.

-u uid Set the owner of the files in the file system to uid. The
default owner is the owner of the directory on which the file
system is being mounted.

-g gid Set the group of the files in the file system to gid. The
default group is the group of the directory on which the file
system is being mounted.

-m mask
Specify the maximum file permissions for files in the file sys-
tem.

FEATURES
NTFS file attributes are accessed in following way:

foo[[:ATTRTYPE]:ATTRNAME]

`ATTRTYPE' is one of the identifiers listed in $AttrDef file of volume.
Default is $DATA. `ATTRNAME' is an attribute name. Default is none.

EXAMPLES
To mount an ntfs volume located in /dev/ad1s1:

# mount_ntfs /dev/ad1s1 /mnt

To get the volume name (in Unicode):

# cat /mnt/\$Volume:\$VOLUME_NAME

To read directory raw data:

# cat /mnt/foodir:\$INDEX_ROOT:\$I30

WRITING
There is limited writing ability. Limitations: file must be nonresident
and must not contain any sparces (uninitialized areas); compressed files
are also not supported.

SEE ALSO
mount(2), unmount(2), fstab(5), mount(8), mount_msdosfs(8)

CAVEATS
This utility is primarily used for read access to an NTFS volume. See
the WRITING section for details about writing to an NTFS volume.

HISTORY
The mount_ntfs utility first appeared in FreeBSD 3.0.

AUTHORS
The NTFS kernel implementation, mount_ntfs utility, and manual were writ-
ten by Semen Ustimenko <semenu@FreeBSD.org>.

BSD November 11, 2004 BSD

---
k:.



[ Reply to This | # ]
Limited Write Support?
Authored by: moritzh on Aug 05, '05 01:32:08PM
I haven't tried it personally, however the manual pages for mount_ntfs state that there is limited write support. It may just be that the automounter doesn't mount the disks read/write for safety reasons, whereas you _may_ be able to mount them read/write via the Terminal.

Here's the man page: (man mount_ntfs)
...
WRITING
There is limited writing ability. Limitations: file must be nonresident and must not contain any sparces (uninitialized areas); compressed files are also not supported.

I submitted the hint more than two months ago [but it was published only now because there were apparently some problems with the hint queue on the the site - Rob is aware of this and wants to publish any other hints soon that have experienced similar problems as mine ]. Thus, and because I don't have 10.4.1 anymore, I am not totally sure, but I believe I saw the same in the manual at that time, but I decided not to try that.

I had done some research on the net about NTFS etc. and saw that Linux has been struggling with writing support for a while and that NTFS is a rather advanced file system (many features). My guess was that Apple probably wouldn't be ahead of all those Linux hackers, so I decided that writing support would probably not realiably work OS X. Personally, I won't try it out because it seems too risky to me (and I don't recommend anyone trying it with important data).



[ Reply to This | # ]