At the moment, it comprises of the mkfs.fat, which is also known as mkfs.msdos or mkfs.vfat, fsck.fat, which also known as fsck.msdos or fsck.vfat, as well as the fatlabel command-line tools.
Getting started with dosfstools
To install and use the dosfstools tools in your GNU/Linux operating system, you must first download the latest version from Softpedia, save the archive on a location of your choice, extract its contents and open a terminal emulator.
On the terminal window, use the ‘cd’ command to navigate to the location of the extracted archive files, and execute the ‘make’ command to compile the source code, follow by the ‘make install’ command as root or with sudo to install the program system wide.
Each of the aforementioned command comes with various command-line options. To see them, you must run each command with the ‘--help’ string. For example, the ‘fatlable’ command accepts two options, the device and the label.
The ‘fsck.fat’ command will help you to automatically repair a filesystem, list path names, perform a verification pass, use DOS codepage to decode short file names, make read-only boot sector checks, toggle the Atari filesystem format or salvage unused chains to files.
On the other hand, the ‘mkfs.fat’ command includes several command-line options that let users to access hidden sectors, backup boot sectors, access reserved sectors, as well as to specify the drive number, logical sector size, volume ID and name, and sectors per cluster.
Supported operating systems and availability
The software is distributed on several Linux operating systems, including Arch Linux, Debian, Dragora, Fedora, Gentoo, Sabayon, T2, and Ubuntu. The source code and access to the latest, bleeding-edge code (via GitHub), as well as detailed usage information can be found on the official homepage of the project.
Reviewed by Marius Nestor, last updated on December 15th, 2014
In a hurry? Add it to your Download Basket!
- fatlabel did not recognize long file names and mistook long file name segments in the root directory for labels. This caused output of garbage when asked to print the label and damage to the root directory (loss of long file name after fsck) when used to set the label.
- A fsck.fat check introduced in 3.0.26 triggered use of uninitialized fields in the constructed root directory entry, which randomly caused the code checking file names to consider the empty "file name" of the root directory to be bad:
Application descriptiondosfstools is an open source and free command-line software project that comprises of various utilities to manage FAT&...