First of all, it might be an idea to check that your kernel understands NTFS. The command below will give a list of all the filesystems that Linux understands. If you see ntfs, then you are OK. Also it might be a good idea to read the mount manual, man 8 mount. cat /proc/filesystems Next you need to create a place to mount the NTFS Volume. Then you can mount it.

Once you are happy with your mount command, you can teach Linux how to mount the volume automatically by adding a line to /etc/fstab (filesystem table). Don't worry about the meaning of the 0 0 on the end. mount /dev/hda1 /mnt/windows -t ntfs -r /dev/hda1 /mnt/windows ntfs ro 0 0 Here we've transformed "-r" into the equivalent "-o ro".

DOS, Windows 95/98/ME: fdisk. Use a boot disk, or ask Windows to go to DOS mode. Then run fdisk. If you have more than one disk, first select that. Then you want to delete a non-DOS partition. Be very careful, your changes will be committed immediately. Windows 2000, XP: Logical Disk Manager. Start at the Control Panel, select Administrative Tools, then Computer Management.

After a volume has been in use for a while, after many writes to the disk, the files can end up fragmented. That is not in one consecutive place on the disk, but in many small pieces. This causes a slowdown when trying to access these files. Windows 2000 and XP have a defragmenting program built in. For users of Windows NT, there is a free program to do the same job. Diskeeper Lite can be downloaded from: http://diskeeper.com

Until recently the only way to resize and NTFS Volume without data loss, was to pay lots of money. Now we have our own program, ntfsresize. It has been tested, but for now it should be considered experimental. For more information, please read the ntfsresize FAQ.

A hidden volume can be mounted the same way as a standard TrueCrypt volume: Click Select File or Select Device to select the outer/host volume (important: make sure the volume is not mounted). Then click Mount, and enter the password for the hidden volume. Whether the hidden or the outer volume will be mounted is determined by the entered password (i.e.

Once you are happy with your mount command, you can teach Linux how to mount the volume automatically by adding a line to /etc/fstab (filesystem table). Don't worry about the meaning of the 0 0 on the end. mount /dev/hda1 /mnt/windows -t ntfs -r /dev/hda1 /mnt/windows ntfs ro 0 0 Here we've transformed -r into the equivalent -o ro.

Not really, but if you only need to copy files from Linux to Windows on a dual-boot machine, see "How to write to NTFS" below for a possible way to work around the lack of write support. For write support in Linux, read on. There are two drivers, currently. The original driver, in 2.4 has some write code in it, but it is extremely dangerous to use it. The possibility of destroying your filesystem is very high. The new driver, introduced in 2.5.11, has some write code, but it's very limited.

Yes, both grub and lilo can boot Windows from an NTFS Volume. What actually happens, is that the Linux boot loader finds the NTFS boot loader and gives control to it.

The simple answer is, "You can't". There is an exception if you have money. Partition Magic, available from http://www.powerquest.com can convert between several filesystems, including NTFS and FAT.

Yes, virtual TrueCrypt volumes (in contrast to TrueCrypt-encrypted physical system partitions/drives) are independent of the operating system. You will be able to mount your TrueCrypt volume on any computer on which you can run TrueCrypt (see also the question "Can I use TrueCrypt on Windows if I do not have administrator privileges?").

Unfortunately, you can't. These versions of Windows can only understand FAT. NTFS can only be read by Windows NT, 2000 and XP. However, with a little work, you can use a couple of utilities from http://www.sysinternals.com "NTFS for Windows 98" and "NTFSDOS" allow you to read NTFS from Windows 95, 98 and DOS. If you are prepared to pay, they even have versions that will write to NTFS (N.B. It is very expensive).

There are three options to control the permissions and ownership of files and directories. They are: umask, uid and gid. They are mentioned in Common mount options. Below are some examples of each option and how it affects the files. We will use the same mount command each time and just show the options. mount /dev/hda1 /mnt/windows -t ntfs -r umask is a filter of permissions, so it works in the opposite way to chmod. Full permissions are equivalent to 777 (rwxrwxrwx).

DOS, Windows 95/98/ME: fdisk. Use a boot disk, or ask Windows to go to DOS mode. Then run fdisk. If you have more than one disk, first select that. Then you want to delete a non-DOS partition. Be very careful, your changes will be committed immediately. Windows 2000, XP and Server 2003: Logical Disk Manager. Start at the Control Panel, select Administrative Tools, then Computer Management.

After a volume has been in use for a while, after many writes to the disk, the files can end up fragmented. That is not in one consecutive place on the disk, but in many small pieces. This causes a slowdown when trying to access these files. Windows 2000, XP and Server 2003 have a defragmenting program built in. For users of Windows NT, there is a free program to do the same job. "Diskeeper Lite" can be downloaded from: http://diskeeper.com/

Use our stable and widely used program, ntfsresize. Or even better, one of the easy-to-use partitioners (DiskDrake, QTParted, YAST, EVMS, Partman, GParted, etc) that integrated it. For more information, please read the ntfsresize FAQ.

You could either use the console or use mount directly. For console, refer to the user's guide. # mount -t ocfs2 /dev/sdX /dir The above command will mount device /dev/sdX on directory /dir.

Once you are happy with your mount command, you can teach Linux how to mount the volume automatically by adding a line to "/etc/fstab" (filesystem table).

Check which kernel version you are using with the command uname -a. If the version is 2.4.9 then it is important for you to update your kernel. See the RedHat Website for more details. If you'd prefer, you could compile your own kernel. See How do I add NTFS support to Linux? for more details.

The Linux-NTFS project provides safe write support in different ways and with different degree of functionality since 2002. first the kernel driver started to support file overwrite which was used by several distributions to install and run Linux from NTFS by loopback mounting an image file, or use it to store private data or configuration files. In the same year, 2002, ntfsresize was developed and in the following year significantly improved to provide safe and full data relocation support.

Not really, but if you only need to copy files from Linux to Windows on a dual-boot machine, see "How to write to NTFS" below for a possible way to work around the lack of write support. For write support in Linux, read on. There are two drivers, currently. The original driver, in 2.4 has some write code in it, but it is extremely dangerous to use it. The possibility of destroying your filesystem is very high. The new driver, introduced in 2.5.11, has some write code, but it's very limited.

Yes, both grub and lilo can boot Windows from an NTFS Volume. What actually happens, is that the Linux boot loader finds the NTFS boot loader and gives control to it.

Open a command window and type (replacing <q>x:</q> with the correct volume): convert x: /fs:ntfs