are utilities to create, check and label (MS-DOS) FAT filesystems.
| README (dosfstools-4.1) | : | README (dosfstools-4.2) |
|---|
| dosfstools consists of the programs mkfs.fat, fsck.fat and fatlabel to create, | | 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 | | 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. | | under the GNU GPL version 3 or later. See the file COPYING for details. |
| | |
| ### Build Requirements | | ### Build Requirements |
| | |
|
| dosfstools recommends libudev. It is used in mkfs.fat to collect additional | | |
| information about the device to format in order to refuse potentially unsafe | | |
| operations without additional confirmation. | | |
| | | |
| The test suite requires the tool xxd (available as part of the vim | | The test suite requires the tool xxd (available as part of the vim |
| distribution). | | distribution). |
| | |
| ### Installing | | ### Installing |
| | |
| dosfstools are built using an autoconf/automake system, so the standard method | | dosfstools are built using an autoconf/automake system, so the standard method |
| applies: | | applies: |
| | |
| ./configure | | ./configure |
| make | | make |
| | |
| skipping to change at line 48 | | skipping to change at line 44 |
|---|
| filesystem the tests are executed on should support sparse files, otherwise the | | filesystem the tests are executed on should support sparse files, otherwise the |
| tests will be resource intensive. | | tests will be resource intensive. |
| | |
| ### Building from the VCS repository | | ### Building from the VCS repository |
| | |
| If you are working directly from a git clone of the official dosfstools | | 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 | | 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 | | because it, like other autogenerated files for the build system, is not included |
| in the repository. | | in the repository. |
| | |
|
| First, autoconf and automake have to be installed. Then you can run | | First, autoconf, automake and gettext have to be installed. Then you can run |
| "autoreconf -i" to generate all the required files. | | "./autogen.sh" to generate all the required files. |
| | | |
| End of changes. 2 change blocks. |
|---|
| 4 lines changed or deleted | | 0 lines changed or added |
|---|
"Fossies" - the Fresh Open Source Software Archive 