https://github.com/dosfstools/dosfstools

dosfstools consists of the programs mkfs.fat, fsck.fat and fatlabel to create, check and label file systems of the FAT family.
https://github.com/dosfstools/dosfstools

c fat filesystem fsck mkfs

Last synced: about 2 months ago
JSON representation

dosfstools consists of the programs mkfs.fat, fsck.fat and fatlabel to create, check and label file systems of the FAT family.

• Host: GitHub
• URL: https://github.com/dosfstools/dosfstools
• Owner: dosfstools
• License: gpl-3.0
• Created: 2014-11-11T00:14:04.000Z (about 10 years ago)
• Default Branch: master
• Last Pushed: 2024-04-13T08:56:07.000Z (9 months ago)
• Last Synced: 2024-08-02T15:34:25.901Z (5 months ago)
• Topics: c, fat, filesystem, fsck, mkfs
• Language: C
• Homepage:
• Size: 1000 KB
• Stars: 257
• Watchers: 13
• Forks: 115
• Open Issues: 36
• Metadata Files:
  • Readme: README
  • Changelog: ChangeLog
  • License: COPYING

Awesome Lists containing this project

README

        
dosfstools consists of the programs mkfs.fat, fsck.fat and fatlabel to create,

check and label file systems of the FAT family.  The dosfstools are licensed

under the GNU GPL version 3 or later. See the file COPYING for details.

### Build Requirements

The test suite requires the tool xxd (available as part of the vim

distribution).

### Installing

dosfstools are built using an autoconf/automake system, so the standard method

applies:

  ./configure

  make

  make install

You need to have superuser privileges in order to install into the standard

system wide locations.

The ./configure script has an option --enable-compat-symlinks that will

configure the build to symlink older names of the tools to the current ones on

installation. These are dosfsck, fsck.msdos and fsck.vfat for fsck.fat, mkdosfs,

mkfs.msdos and mkfs.vfat for mkfs.fat and dosfslabel for fatlabel.

### Running the test suite

The test suite can be run with "make check" after configuring. Note that if

xxd isn't available, all tests will be skipped and nothing actually tested.

During the tests temporary files of multiple GB in size will be created, but the

actual data content is not more than a few MB. The operating system and the

filesystem the tests are executed on should support sparse files, otherwise the

tests will be resource intensive.

### Building from the VCS repository

If you are working directly from a git clone of the official dosfstools

repository, you will find that you can not run "./configure" straight away

because it, like other autogenerated files for the build system, is not included

in the repository.

First, autoconf, automake and gettext have to be installed.  Then you can run

"./autogen.sh" to generate all the required files.