Kconfig 5.0 KB

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