mirror of
https://github.com/reactos/reactos.git
synced 2025-05-23 11:04:52 +00:00
b0bf7dfb62
It's critical not to perform any write on a volume without an exclusive lock on it. That lock is only acquired if ChkDsk is started in RW mode. Also added an assert in write routine, to make sure that when we're about to perform a write operation, we're really allowed to do so. This will avoid volume corruptions when a simple "chkdsk" is issued from cmd. To put it simple: check will really check now, and won't attempt any repair. CORE-14119 |
||
|---|---|---|
| .. | ||
| boot.c | ||
| boot.h | ||
| byteorder.h | ||
| byteswap.h | ||
| byteswap1.h | ||
| ChangeLog | ||
| check.c | ||
| check.h | ||
| common.c | ||
| common.h | ||
| compiler.h | ||
| COPYING | ||
| dosfsck.h | ||
| fat.c | ||
| fat.h | ||
| file.c | ||
| file.h | ||
| fsck.fat.h | ||
| io.c | ||
| io.h | ||
| lfn.c | ||
| lfn.h | ||
| msdos_fs.h | ||
| README | ||
| rosglue.h | ||
| swab.h | ||
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 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. ### 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. ### 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 and automake have to be installed. Then you can run "autoreconf -i" to generate all the required files.