1 # SPDX-License-Identifier: GPL-2.0-only <<
2 config FAT_FS 1 config FAT_FS
3 tristate 2 tristate
4 select BUFFER_HEAD <<
5 select NLS 3 select NLS
6 select LEGACY_DIRECT_IO <<
7 help 4 help
8 If you want to use one of the FAT-ba 5 If you want to use one of the FAT-based file systems (the MS-DOS and
9 VFAT (Windows 95) file systems), the 6 VFAT (Windows 95) file systems), then you must say Y or M here
10 to include FAT support. You will the 7 to include FAT support. You will then be able to mount partitions or
11 diskettes with FAT-based file system 8 diskettes with FAT-based file systems and transparently access the
12 files on them, i.e. MSDOS files will 9 files on them, i.e. MSDOS files will look and behave just like all
13 other Unix files. 10 other Unix files.
14 11
15 This FAT support is not a file syste 12 This FAT support is not a file system in itself, it only provides
16 the foundation for the other file sy 13 the foundation for the other file systems. You will have to say Y or
17 M to at least one of "MSDOS fs suppo 14 M to at least one of "MSDOS fs support" or "VFAT fs support" in
18 order to make use of it. 15 order to make use of it.
19 16
20 Another way to read and write MSDOS 17 Another way to read and write MSDOS floppies and hard drive
21 partitions from within Linux (but no 18 partitions from within Linux (but not transparently) is with the
22 mtools ("man mtools") program suite. 19 mtools ("man mtools") program suite. You don't need to say Y here in
23 order to do that. 20 order to do that.
24 21
25 If you need to move large files on f 22 If you need to move large files on floppies between a DOS and a
26 Linux box, say Y here, mount the flo 23 Linux box, say Y here, mount the floppy under Linux with an MSDOS
27 file system and use GNU tar's M opti 24 file system and use GNU tar's M option. GNU tar is a program
28 available for Unix and DOS ("man tar 25 available for Unix and DOS ("man tar" or "info tar").
29 26
30 The FAT support will enlarge your ke 27 The FAT support will enlarge your kernel by about 37 KB. If unsure,
31 say Y. 28 say Y.
32 29
33 To compile this as a module, choose 30 To compile this as a module, choose M here: the module will be called
34 fat. Note that if you compile the F 31 fat. Note that if you compile the FAT support as a module, you
35 cannot compile any of the FAT-based 32 cannot compile any of the FAT-based file systems into the kernel
36 -- they will have to be modules as w 33 -- they will have to be modules as well.
37 34
38 config MSDOS_FS 35 config MSDOS_FS
39 tristate "MSDOS fs support" 36 tristate "MSDOS fs support"
40 select FAT_FS 37 select FAT_FS
41 help 38 help
42 This allows you to mount MSDOS parti 39 This allows you to mount MSDOS partitions of your hard drive (unless
43 they are compressed; to access compr 40 they are compressed; to access compressed MSDOS partitions under
44 Linux, you can either use the DOS em 41 Linux, you can either use the DOS emulator DOSEMU, described in the
45 DOSEMU-HOWTO, available from 42 DOSEMU-HOWTO, available from
46 <https://www.tldp.org/docs.html#howt !! 43 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
47 <ftp://ibiblio.org/pub/Linux/system/ 44 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
48 intend to use dosemu with a non-comp 45 intend to use dosemu with a non-compressed MSDOS partition, say Y
49 here) and MSDOS floppies. This means 46 here) and MSDOS floppies. This means that file access becomes
50 transparent, i.e. the MSDOS files lo 47 transparent, i.e. the MSDOS files look and behave just like all
51 other Unix files. 48 other Unix files.
52 49
53 If you have Windows 95 or Windows NT 50 If you have Windows 95 or Windows NT installed on your MSDOS
54 partitions, you should use the VFAT 51 partitions, you should use the VFAT file system (say Y to "VFAT fs
55 support" below), or you will not be 52 support" below), or you will not be able to see the long filenames
56 generated by Windows 95 / Windows NT 53 generated by Windows 95 / Windows NT.
57 54
58 This option will enlarge your kernel 55 This option will enlarge your kernel by about 7 KB. If unsure,
59 answer Y. This will only work if you 56 answer Y. This will only work if you said Y to "DOS FAT fs support"
60 as well. To compile this as a module 57 as well. To compile this as a module, choose M here: the module will
61 be called msdos. 58 be called msdos.
62 59
63 config VFAT_FS 60 config VFAT_FS
64 tristate "VFAT (Windows-95) fs support 61 tristate "VFAT (Windows-95) fs support"
65 select FAT_FS 62 select FAT_FS
66 help 63 help
67 This option provides support for nor 64 This option provides support for normal Windows file systems with
68 long filenames. That includes non-c 65 long filenames. That includes non-compressed FAT-based file systems
69 used by Windows 95, Windows 98, Wind 66 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
70 programs from the mtools package. 67 programs from the mtools package.
71 68
72 The VFAT support enlarges your kerne 69 The VFAT support enlarges your kernel by about 10 KB and it only
73 works if you said Y to the "DOS FAT 70 works if you said Y to the "DOS FAT fs support" above. Please read
74 the file <file:Documentation/filesys !! 71 the file <file:Documentation/filesystems/vfat.txt> for details. If
75 unsure, say Y. 72 unsure, say Y.
76 73
77 To compile this as a module, choose 74 To compile this as a module, choose M here: the module will be called
78 vfat. 75 vfat.
79 76
80 config FAT_DEFAULT_CODEPAGE 77 config FAT_DEFAULT_CODEPAGE
81 int "Default codepage for FAT" 78 int "Default codepage for FAT"
82 depends on FAT_FS !! 79 depends on MSDOS_FS || VFAT_FS
83 default 437 80 default 437
84 help 81 help
85 This option should be set to the cod 82 This option should be set to the codepage of your FAT filesystems.
86 It can be overridden with the "codep 83 It can be overridden with the "codepage" mount option.
87 See <file:Documentation/filesystems/ !! 84 See <file:Documentation/filesystems/vfat.txt> for more information.
88 85
89 config FAT_DEFAULT_IOCHARSET 86 config FAT_DEFAULT_IOCHARSET
90 string "Default iocharset for FAT" 87 string "Default iocharset for FAT"
91 depends on VFAT_FS 88 depends on VFAT_FS
92 default "iso8859-1" 89 default "iso8859-1"
93 help 90 help
94 Set this to the default input/output 91 Set this to the default input/output character set you'd
95 like FAT to use. It should probably 92 like FAT to use. It should probably match the character set
96 that most of your FAT filesystems us 93 that most of your FAT filesystems use, and can be overridden
97 with the "iocharset" mount option fo 94 with the "iocharset" mount option for FAT filesystems.
98 Note that "utf8" is not recommended 95 Note that "utf8" is not recommended for FAT filesystems.
99 If unsure, you shouldn't set "utf8" !! 96 If unsure, you shouldn't set "utf8" here.
100 instead if you would like to use UTF !! 97 See <file:Documentation/filesystems/vfat.txt> for more information.
101 See <file:Documentation/filesystems/ <<
102 98
103 Enable any character sets you need i 99 Enable any character sets you need in File Systems/Native Language
104 Support. 100 Support.
105 <<
106 config FAT_DEFAULT_UTF8 <<
107 bool "Enable FAT UTF-8 option by defau <<
108 depends on VFAT_FS <<
109 default n <<
110 help <<
111 Set this if you would like to have " <<
112 by default when mounting FAT filesys <<
113 <<
114 Even if you say Y here can always di <<
115 particular mount by adding "utf8=0" <<
116 <<
117 Say Y if you use UTF-8 encoding for <<
118 <<
119 See <file:Documentation/filesystems/ <<
120 <<
121 config FAT_KUNIT_TEST <<
122 tristate "Unit Tests for FAT filesyste <<
123 depends on KUNIT && FAT_FS <<
124 default KUNIT_ALL_TESTS <<
125 help <<
126 This builds the FAT KUnit tests <<
127 <<
128 For more information on KUnit and un <<
129 to the KUnit documentation in Docume <<
130 <<
131 If unsure, say N <<
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.