€•Œsphinx.addnodes”Œdocument”“”)�”}”(Œ rawsource”Œ”Œchildren”]”(Œ translations”Œ LanguagesNode”“”)�”}”(hhh]”(hŒ pending_xref”“”)�”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…”�”}”Œparent”hsbaŒ attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ refdomain”Œstd”Œreftype”Œdoc”Œ reftarget”Œ$/translations/zh_CN/filesystems/vfat”Œmodname”NŒ classname”NŒ refexplicit”ˆuŒtagname”hhh ubh)�”}”(hhh]”hŒChinese (Traditional)”…”�”}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ$/translations/zh_TW/filesystems/vfat”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)�”}”(hhh]”hŒItalian”…”�”}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ$/translations/it_IT/filesystems/vfat”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)�”}”(hhh]”hŒJapanese”…”�”}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ$/translations/ja_JP/filesystems/vfat”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)�”}”(hhh]”hŒKorean”…”�”}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ$/translations/ko_KR/filesystems/vfat”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)�”}”(hhh]”hŒPortuguese (Brazilian)”…”�”}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ$/translations/pt_BR/filesystems/vfat”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)�”}”(hhh]”hŒSpanish”…”�”}”hh–sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ$/translations/sp_SP/filesystems/vfat”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h hhŒ _document”hŒsource”NŒline”NubhŒsection”“”)�”}”(hhh]”(hŒtitle”“”)�”}”(hŒVFAT”h]”hŒVFAT”…”�”}”(hh¼h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhh·h²hh³Œ>/var/lib/git/docbuild/linux/Documentation/filesystems/vfat.rst”h´Kubh¶)�”}”(hhh]”(h»)�”}”(hŒ USING VFAT”h]”hŒ USING VFAT”…”�”}”(hhÎh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhhËh²hh³hÊh´KubhŒ paragraph”“”)�”}”(hŒCTo use the vfat filesystem, use the filesystem type 'vfat'. i.e.::”h]”hŒFTo use the vfat filesystem, use the filesystem type ‘vfat’. i.e.:”…”�”}”(hhÞh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KhhËh²hubhŒ literal_block”“”)�”}”(hŒmount -t vfat /dev/fd0 /mnt”h]”hŒmount -t vfat /dev/fd0 /mnt”…”�”}”hhîsbah}”(h]”h ]”h"]”h$]”h&]”Œ xml:space”Œpreserve”uh1hìh³hÊh´K hhËh²hubhÝ)�”}”(hŒmNo special partition formatter is required, 'mkdosfs' will work fine if you want to format from within Linux.”h]”hŒqNo special partition formatter is required, ‘mkdosfs’ will work fine if you want to format from within Linux.”…”�”}”(hhþh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K hhËh²hubeh}”(h]”Œ using-vfat”ah ]”h"]”Œ using vfat”ah$]”h&]”uh1hµhh·h²hh³hÊh´Kubh¶)�”}”(hhh]”(h»)�”}”(hŒVFAT MOUNT OPTIONS”h]”hŒVFAT MOUNT OPTIONS”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjh²hh³hÊh´KubhŒdefinition_list”“”)�”}”(hhh]”(hŒdefinition_list_item”“”)�”}”(hŒf**uid=###** Set the owner of all files on this filesystem. The default is the uid of current process. ”h]”(hŒterm”“”)�”}”(hŒ **uid=###**”h]”hŒstrong”“”)�”}”(hj4h]”hŒuid=###”…”�”}”(hj8h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hj2ubah}”(h]”h ]”h"]”h$]”h&]”uh1j0h³hÊh´Khj,ubhŒ definition”“”)�”}”(hhh]”hÝ)�”}”(hŒYSet the owner of all files on this filesystem. The default is the uid of current process.”h]”hŒYSet the owner of all files on this filesystem. The default is the uid of current process.”…”�”}”(hjPh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KhjMubah}”(h]”h ]”h"]”h$]”h&]”uh1jKhj,ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j*h³hÊh´Khj'ubj+)�”}”(hŒf**gid=###** Set the group of all files on this filesystem. The default is the gid of current process. ”h]”(j1)�”}”(hŒ **gid=###**”h]”j7)�”}”(hjph]”hŒgid=###”…”�”}”(hjrh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hjnubah}”(h]”h ]”h"]”h$]”h&]”uh1j0h³hÊh´KhjjubjL)�”}”(hhh]”hÝ)�”}”(hŒYSet the group of all files on this filesystem. The default is the gid of current process.”h]”hŒYSet the group of all files on this filesystem. The default is the gid of current process.”…”�”}”(hjˆh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Khj…ubah}”(h]”h ]”h"]”h$]”h&]”uh1jKhjjubeh}”(h]”h ]”h"]”h$]”h&]”uh1j*h³hÊh´Khj'h²hubj+)�”}”(hŒ|**umask=###** The permission mask (for files and directories, see *umask(1)*). The default is the umask of current process. ”h]”(j1)�”}”(hŒ **umask=###**”h]”j7)�”}”(hj¨h]”hŒ umask=###”…”�”}”(hjªh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hj¦ubah}”(h]”h ]”h"]”h$]”h&]”uh1j0h³hÊh´Khj¢ubjL)�”}”(hhh]”hÝ)�”}”(hŒmThe permission mask (for files and directories, see *umask(1)*). The default is the umask of current process.”h]”(hŒ4The permission mask (for files and directories, see ”…”�”}”(hjÀh²hh³Nh´NubhŒemphasis”“”)�”}”(hŒ *umask(1)*”h]”hŒumask(1)”…”�”}”(hjÊh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÈhjÀubhŒ/). The default is the umask of current process.”…”�”}”(hjÀh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Khj½ubah}”(h]”h ]”h"]”h$]”h&]”uh1jKhj¢ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j*h³hÊh´Khj'h²hubj+)�”}”(hŒb**dmask=###** The permission mask for the directory. The default is the umask of current process. ”h]”(j1)�”}”(hŒ **dmask=###**”h]”j7)�”}”(hjôh]”hŒ dmask=###”…”�”}”(hjöh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hjòubah}”(h]”h ]”h"]”h$]”h&]”uh1j0h³hÊh´K!hjîubjL)�”}”(hhh]”hÝ)�”}”(hŒSThe permission mask for the directory. The default is the umask of current process.”h]”hŒSThe permission mask for the directory. The default is the umask of current process.”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K hj ubah}”(h]”h ]”h"]”h$]”h&]”uh1jKhjîubeh}”(h]”h ]”h"]”h$]”h&]”uh1j*h³hÊh´K!hj'h²hubj+)�”}”(hŒZ**fmask=###** The permission mask for files. The default is the umask of current process. ”h]”(j1)�”}”(hŒ **fmask=###**”h]”j7)�”}”(hj,h]”hŒ fmask=###”…”�”}”(hj.h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hj*ubah}”(h]”h ]”h"]”h$]”h&]”uh1j0h³hÊh´K%hj&ubjL)�”}”(hhh]”hÝ)�”}”(hŒKThe permission mask for files. The default is the umask of current process.”h]”hŒKThe permission mask for files. The default is the umask of current process.”…”�”}”(hjDh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K$hjAubah}”(h]”h ]”h"]”h$]”h&]”uh1jKhj&ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j*h³hÊh´K%hj'h²hubj+)�”}”(hX2**allow_utime=###** This option controls the permission check of mtime/atime. **-20**: If current process is in group of file's group ID, you can change timestamp. **-2**: Other users can change timestamp. The default is set from dmask option. If the directory is writable, utime(2) is also allowed. i.e. ~dmask & 022. Normally utime(2) checks current process is owner of the file, or it has CAP_FOWNER capability. But FAT filesystem doesn't have uid/gid on disk, so normal check is too inflexible. With this option you can relax it. ”h]”(j1)�”}”(hŒ**allow_utime=###**”h]”j7)�”}”(hjdh]”hŒallow_utime=###”…”�”}”(hjfh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hjbubah}”(h]”h ]”h"]”h$]”h&]”uh1j0h³hÊh´K6hj^ubjL)�”}”(hhh]”(hÝ)�”}”(hŒ9This option controls the permission check of mtime/atime.”h]”hŒ9This option controls the permission check of mtime/atime.”…”�”}”(hj|h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K(hjyubhŒ block_quote”“”)�”}”(hŒ�**-20**: If current process is in group of file's group ID, you can change timestamp. **-2**: Other users can change timestamp. ”h]”(hÝ)�”}”(hŒU**-20**: If current process is in group of file's group ID, you can change timestamp.”h]”(j7)�”}”(hŒ**-20**”h]”hŒ-20”…”�”}”(hj”h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hj�ubhŒP: If current process is in group of file’s group ID, you can change timestamp.”…”�”}”(hj�h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K*hjŒubhÝ)�”}”(hŒ)**-2**: Other users can change timestamp.”h]”(j7)�”}”(hŒ**-2**”h]”hŒ-2”…”�”}”(hj°h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hj¬ubhŒ#: Other users can change timestamp.”…”�”}”(hj¬h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K-hjŒubeh}”(h]”h ]”h"]”h$]”h&]”uh1jŠh³hÊh´K*hjyubhÝ)�”}”(hŒpThe default is set from dmask option. If the directory is writable, utime(2) is also allowed. i.e. ~dmask & 022.”h]”hŒpThe default is set from dmask option. If the directory is writable, utime(2) is also allowed. i.e. ~dmask & 022.”…”�”}”(hjÎh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K/hjyubhÝ)�”}”(hŒÖNormally utime(2) checks current process is owner of the file, or it has CAP_FOWNER capability. But FAT filesystem doesn't have uid/gid on disk, so normal check is too inflexible. With this option you can relax it.”h]”hŒØNormally utime(2) checks current process is owner of the file, or it has CAP_FOWNER capability. But FAT filesystem doesn’t have uid/gid on disk, so normal check is too inflexible. With this option you can relax it.”…”�”}”(hjÜh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K2hjyubeh}”(h]”h ]”h"]”h$]”h&]”uh1jKhj^ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j*h³hÊh´K6hj'h²hubj+)�”}”(hŒ–**codepage=###** Sets the codepage number for converting to shortname characters on FAT filesystem. By default, FAT_DEFAULT_CODEPAGE setting is used. ”h]”(j1)�”}”(hŒ**codepage=###**”h]”j7)�”}”(hjüh]”hŒ codepage=###”…”�”}”(hjþh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hjúubah}”(h]”h ]”h"]”h$]”h&]”uh1j0h³hÊh´K;hjöubjL)�”}”(hhh]”hÝ)�”}”(hŒ„Sets the codepage number for converting to shortname characters on FAT filesystem. By default, FAT_DEFAULT_CODEPAGE setting is used.”h]”hŒ„Sets the codepage number for converting to shortname characters on FAT filesystem. By default, FAT_DEFAULT_CODEPAGE setting is used.”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K9hjubah}”(h]”h ]”h"]”h$]”h&]”uh1jKhjöubeh}”(h]”h ]”h"]”h$]”h&]”uh1j*h³hÊh´K;hj'h²hubj+)�”}”(hX„**iocharset=** Character set to use for converting between the encoding is used for user visible filename and 16 bit Unicode characters. Long filenames are stored on disk in Unicode format, but Unix for the most part doesn't know how to deal with Unicode. By default, FAT_DEFAULT_IOCHARSET setting is used. There is also an option of doing UTF-8 translations with the utf8 option. ”h]”(j1)�”}”(hŒ**iocharset=**”h]”j7)�”}”(hj4h]”hŒiocharset=”…”�”}”(hj6h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hj2ubah}”(h]”h ]”h"]”h$]”h&]”uh1j0h³hÊh´KFhj.ubjL)�”}”(hhh]”(hÝ)�”}”(hX#Character set to use for converting between the encoding is used for user visible filename and 16 bit Unicode characters. Long filenames are stored on disk in Unicode format, but Unix for the most part doesn't know how to deal with Unicode. By default, FAT_DEFAULT_IOCHARSET setting is used.”h]”hX%Character set to use for converting between the encoding is used for user visible filename and 16 bit Unicode characters. Long filenames are stored on disk in Unicode format, but Unix for the most part doesn’t know how to deal with Unicode. By default, FAT_DEFAULT_IOCHARSET setting is used.”…”�”}”(hjLh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K>hjIubhÝ)�”}”(hŒIThere is also an option of doing UTF-8 translations with the utf8 option.”h]”hŒIThere is also an option of doing UTF-8 translations with the utf8 option.”…”�”}”(hjZh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KEhjIubeh}”(h]”h ]”h"]”h$]”h&]”uh1jKhj.ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j*h³hÊh´KFhj'h²hubeh}”(h]”h ]”h"]”h$]”h&]”uh1j%hjh²hh³hÊh´NubhŒnote”“”)�”}”(hŒ^``iocharset=utf8`` is not recommended. If unsure, you should consider the utf8 option instead.”h]”hÝ)�”}”(hŒ^``iocharset=utf8`` is not recommended. If unsure, you should consider the utf8 option instead.”h]”(hŒliteral”“”)�”}”(hŒ``iocharset=utf8``”h]”hŒiocharset=utf8”…”�”}”(hj†h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j„hj€ubhŒL is not recommended. If unsure, you should consider the utf8 option instead.”…”�”}”(hj€h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KHhj|ubah}”(h]”h ]”h"]”h$]”h&]”uh1jzhjh²hh³hÊh´Nubj&)�”}”(hhh]”(j+)�”}”(hŒü**utf8=** UTF-8 is the filesystem safe version of Unicode that is used by the console. It can be enabled or disabled for the filesystem with this option. If 'uni_xlate' gets set, UTF-8 gets disabled. By default, FAT_DEFAULT_UTF8 setting is used. ”h]”(j1)�”}”(hŒ**utf8=**”h]”j7)�”}”(hj­h]”hŒ utf8=”…”�”}”(hj¯h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hj«ubah}”(h]”h ]”h"]”h$]”h&]”uh1j0h³hÊh´KPhj§ubjL)�”}”(hhh]”hÝ)�”}”(hŒëUTF-8 is the filesystem safe version of Unicode that is used by the console. It can be enabled or disabled for the filesystem with this option. If 'uni_xlate' gets set, UTF-8 gets disabled. By default, FAT_DEFAULT_UTF8 setting is used.”h]”hŒïUTF-8 is the filesystem safe version of Unicode that is used by the console. It can be enabled or disabled for the filesystem with this option. If ‘uni_xlate’ gets set, UTF-8 gets disabled. By default, FAT_DEFAULT_UTF8 setting is used.”…”�”}”(hjÅh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KLhjÂubah}”(h]”h ]”h"]”h$]”h&]”uh1jKhj§ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j*h³hÊh´KPhj¤ubj+)�”}”(hXñ**uni_xlate=** Translate unhandled Unicode characters to special escaped sequences. This would let you backup and restore filenames that are created with any Unicode characters. Until Linux supports Unicode for real, this gives you an alternative. Without this option, a '?' is used when no translation is possible. The escape character is ':' because it is otherwise illegal on the vfat filesystem. The escape sequence that gets used is ':' and the four digits of hexadecimal unicode. ”h]”(j1)�”}”(hŒ**uni_xlate=**”h]”j7)�”}”(hjåh]”hŒuni_xlate=”…”�”}”(hjçh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hjãubah}”(h]”h ]”h"]”h$]”h&]”uh1j0h³hÊh´K\hjßubjL)�”}”(hhh]”hÝ)�”}”(hXÛTranslate unhandled Unicode characters to special escaped sequences. This would let you backup and restore filenames that are created with any Unicode characters. Until Linux supports Unicode for real, this gives you an alternative. Without this option, a '?' is used when no translation is possible. The escape character is ':' because it is otherwise illegal on the vfat filesystem. The escape sequence that gets used is ':' and the four digits of hexadecimal unicode.”h]”hXçTranslate unhandled Unicode characters to special escaped sequences. This would let you backup and restore filenames that are created with any Unicode characters. Until Linux supports Unicode for real, this gives you an alternative. Without this option, a ‘?’ is used when no translation is possible. The escape character is ‘:’ because it is otherwise illegal on the vfat filesystem. The escape sequence that gets used is ‘:’ and the four digits of hexadecimal unicode.”…”�”}”(hjýh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KShjúubah}”(h]”h ]”h"]”h$]”h&]”uh1jKhjßubeh}”(h]”h ]”h"]”h$]”h&]”uh1j*h³hÊh´K\hj¤h²hubj+)�”}”(hX5**nonumtail=** When creating 8.3 aliases, normally the alias will end in '~1' or tilde followed by some number. If this option is set, then if the filename is "longfilename.txt" and "longfile.txt" does not currently exist in the directory, longfile.txt will be the short alias instead of longfi~1.txt. ”h]”(j1)�”}”(hŒ**nonumtail=**”h]”j7)�”}”(hjh]”hŒnonumtail=”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hjubah}”(h]”h ]”h"]”h$]”h&]”uh1j0h³hÊh´KdhjubjL)�”}”(hhh]”hÝ)�”}”(hXWhen creating 8.3 aliases, normally the alias will end in '~1' or tilde followed by some number. If this option is set, then if the filename is "longfilename.txt" and "longfile.txt" does not currently exist in the directory, longfile.txt will be the short alias instead of longfi~1.txt.”h]”hX+When creating 8.3 aliases, normally the alias will end in ‘~1’ or tilde followed by some number. If this option is set, then if the filename is “longfilename.txtâ€� and “longfile.txtâ€� does not currently exist in the directory, longfile.txt will be the short alias instead of longfi~1.txt.”…”�”}”(hj5h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K_hj2ubah}”(h]”h ]”h"]”h$]”h&]”uh1jKhjubeh}”(h]”h ]”h"]”h$]”h&]”uh1j*h³hÊh´Kdhj¤h²hubj+)�”}”(hXK**usefree** Use the "free clusters" value stored on FSINFO. It will be used to determine number of free clusters without scanning disk. But it's not used by default, because recent Windows don't update it correctly in some case. If you are sure the "free clusters" on FSINFO is correct, by this option you can avoid scanning disk. ”h]”(j1)�”}”(hŒ **usefree**”h]”j7)�”}”(hjUh]”hŒusefree”…”�”}”(hjWh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hjSubah}”(h]”h ]”h"]”h$]”h&]”uh1j0h³hÊh´KlhjOubjL)�”}”(hhh]”hÝ)�”}”(hX>Use the "free clusters" value stored on FSINFO. It will be used to determine number of free clusters without scanning disk. But it's not used by default, because recent Windows don't update it correctly in some case. If you are sure the "free clusters" on FSINFO is correct, by this option you can avoid scanning disk.”h]”hXJUse the “free clustersâ€� value stored on FSINFO. It will be used to determine number of free clusters without scanning disk. But it’s not used by default, because recent Windows don’t update it correctly in some case. If you are sure the “free clustersâ€� on FSINFO is correct, by this option you can avoid scanning disk.”…”�”}”(hjmh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Kghjjubah}”(h]”h ]”h"]”h$]”h&]”uh1jKhjOubeh}”(h]”h ]”h"]”h$]”h&]”uh1j*h³hÊh´Klhj¤h²hubj+)�”}”(hŒ3**quiet** Stops printing certain warning messages. ”h]”(j1)�”}”(hŒ **quiet**”h]”j7)�”}”(hj�h]”hŒquiet”…”�”}”(hj�h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hj‹ubah}”(h]”h ]”h"]”h$]”h&]”uh1j0h³hÊh´Kohj‡ubjL)�”}”(hhh]”hÝ)�”}”(hŒ(Stops printing certain warning messages.”h]”hŒ(Stops printing certain warning messages.”…”�”}”(hj¥h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Kohj¢ubah}”(h]”h ]”h"]”h$]”h&]”uh1jKhj‡ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j*h³hÊh´Kohj¤h²hubj+)�”}”(hŒ°**check=s|r|n** Case sensitivity checking setting. **s**: strict, case sensitive **r**: relaxed, case insensitive **n**: normal, default setting, currently case insensitive ”h]”(j1)�”}”(hŒ**check=s|r|n**”h]”j7)�”}”(hjÅh]”hŒ check=s|r|n”…”�”}”(hjÇh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hjÃubah}”(h]”h ]”h"]”h$]”h&]”uh1j0h³hÊh´Kxhj¿ubjL)�”}”(hhh]”(hÝ)�”}”(hŒ"Case sensitivity checking setting.”h]”hŒ"Case sensitivity checking setting.”…”�”}”(hjÝh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KrhjÚubhÝ)�”}”(hŒ**s**: strict, case sensitive”h]”(j7)�”}”(hŒ**s**”h]”hŒs”…”�”}”(hjïh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hjëubhŒ: strict, case sensitive”…”�”}”(hjëh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KthjÚubhÝ)�”}”(hŒ **r**: relaxed, case insensitive”h]”(j7)�”}”(hŒ**r**”h]”hŒr”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hjubhŒ: relaxed, case insensitive”…”�”}”(hjh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KvhjÚubhÝ)�”}”(hŒ:**n**: normal, default setting, currently case insensitive”h]”(j7)�”}”(hŒ**n**”h]”hŒn”…”�”}”(hj'h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hj#ubhŒ5: normal, default setting, currently case insensitive”…”�”}”(hj#h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KxhjÚubeh}”(h]”h ]”h"]”h$]”h&]”uh1jKhj¿ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j*h³hÊh´Kxhj¤h²hubj+)�”}”(hŒJ**nocase** This was deprecated for vfat. Use ``shortname=win95`` instead. ”h]”(j1)�”}”(hŒ **nocase**”h]”j7)�”}”(hjQh]”hŒnocase”…”�”}”(hjSh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hjOubah}”(h]”h ]”h"]”h$]”h&]”uh1j0h³hÊh´K{hjKubjL)�”}”(hhh]”hÝ)�”}”(hŒ>This was deprecated for vfat. Use ``shortname=win95`` instead.”h]”(hŒ"This was deprecated for vfat. Use ”…”�”}”(hjih²hh³Nh´Nubj…)�”}”(hŒ``shortname=win95``”h]”hŒshortname=win95”…”�”}”(hjqh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j„hjiubhŒ instead.”…”�”}”(hjih²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K{hjfubah}”(h]”h ]”h"]”h$]”h&]”uh1jKhjKubeh}”(h]”h ]”h"]”h$]”h&]”uh1j*h³hÊh´K{hj¤h²hubj+)�”}”(hX�**shortname=lower|win95|winnt|mixed** Shortname display/create setting. **lower**: convert to lowercase for display, emulate the Windows 95 rule for create. **win95**: emulate the Windows 95 rule for display/create. **winnt**: emulate the Windows NT rule for display/create. **mixed**: emulate the Windows NT rule for display, emulate the Windows 95 rule for create. Default setting is `mixed`. ”h]”(j1)�”}”(hŒ%**shortname=lower|win95|winnt|mixed**”h]”j7)�”}”(hj›h]”hŒ!shortname=lower|win95|winnt|mixed”…”�”}”(hj�h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hj™ubah}”(h]”h ]”h"]”h$]”h&]”uh1j0h³hÊh´KŠhj•ubjL)�”}”(hhh]”(hÝ)�”}”(hŒ!Shortname display/create setting.”h]”hŒ!Shortname display/create setting.”…”�”}”(hj³h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K~hj°ubhÝ)�”}”(hŒT**lower**: convert to lowercase for display, emulate the Windows 95 rule for create.”h]”(j7)�”}”(hŒ **lower**”h]”hŒlower”…”�”}”(hjÅh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hjÁubhŒK: convert to lowercase for display, emulate the Windows 95 rule for create.”…”�”}”(hjÁh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K€hj°ubhÝ)�”}”(hŒ:**win95**: emulate the Windows 95 rule for display/create.”h]”(j7)�”}”(hŒ **win95**”h]”hŒwin95”…”�”}”(hjáh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hjÝubhŒ1: emulate the Windows 95 rule for display/create.”…”�”}”(hjÝh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Kƒhj°ubhÝ)�”}”(hŒ:**winnt**: emulate the Windows NT rule for display/create.”h]”(j7)�”}”(hŒ **winnt**”h]”hŒwinnt”…”�”}”(hjýh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hjùubhŒ1: emulate the Windows NT rule for display/create.”…”�”}”(hjùh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K…hj°ubhÝ)�”}”(hŒ[**mixed**: emulate the Windows NT rule for display, emulate the Windows 95 rule for create.”h]”(j7)�”}”(hŒ **mixed**”h]”hŒmixed”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hjubhŒR: emulate the Windows NT rule for display, emulate the Windows 95 rule for create.”…”�”}”(hjh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K‡hj°ubhÝ)�”}”(hŒDefault setting is `mixed`.”h]”(hŒDefault setting is ”…”�”}”(hj1h²hh³Nh´NubhŒtitle_reference”“”)�”}”(hŒ`mixed`”h]”hŒmixed”…”�”}”(hj;h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j9hj1ubhŒ.”…”�”}”(hj1h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KŠhj°ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jKhj•ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j*h³hÊh´KŠhj¤h²hubj+)�”}”(hXS**tz=UTC** Interpret timestamps as UTC rather than local time. This option disables the conversion of timestamps between local time (as used by Windows on FAT) and UTC (which Linux uses internally). This is particularly useful when mounting devices (like digital cameras) that are set to UTC in order to avoid the pitfalls of local time. ”h]”(j1)�”}”(hŒ **tz=UTC**”h]”j7)�”}”(hjeh]”hŒtz=UTC”…”�”}”(hjgh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hjcubah}”(h]”h ]”h"]”h$]”h&]”uh1j0h³hÊh´K“hj_ubjL)�”}”(hhh]”hÝ)�”}”(hXGInterpret timestamps as UTC rather than local time. This option disables the conversion of timestamps between local time (as used by Windows on FAT) and UTC (which Linux uses internally). This is particularly useful when mounting devices (like digital cameras) that are set to UTC in order to avoid the pitfalls of local time.”h]”hXGInterpret timestamps as UTC rather than local time. This option disables the conversion of timestamps between local time (as used by Windows on FAT) and UTC (which Linux uses internally). This is particularly useful when mounting devices (like digital cameras) that are set to UTC in order to avoid the pitfalls of local time.”…”�”}”(hj}h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K�hjzubah}”(h]”h ]”h"]”h$]”h&]”uh1jKhj_ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j*h³hÊh´K“hj¤h²hubj+)�”}”(hXÑ**time_offset=minutes** Set offset for conversion of timestamps from local time used by FAT to UTC. I.e. minutes will be subtracted from each timestamp to convert it to UTC used internally by Linux. This is useful when time zone set in ``sys_tz`` is not the time zone used by the filesystem. Note that this option still does not provide correct time stamps in all cases in presence of DST - time stamps in a different DST setting will be off by one hour. ”h]”(j1)�”}”(hŒ**time_offset=minutes**”h]”j7)�”}”(hj�h]”hŒtime_offset=minutes”…”�”}”(hjŸh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hj›ubah}”(h]”h ]”h"]”h$]”h&]”uh1j0h³hÊh´K�hj—ubjL)�”}”(hhh]”hÝ)�”}”(hX¸Set offset for conversion of timestamps from local time used by FAT to UTC. I.e. minutes will be subtracted from each timestamp to convert it to UTC used internally by Linux. This is useful when time zone set in ``sys_tz`` is not the time zone used by the filesystem. Note that this option still does not provide correct time stamps in all cases in presence of DST - time stamps in a different DST setting will be off by one hour.”h]”(hŒÞSet offset for conversion of timestamps from local time used by FAT to UTC. I.e. minutes will be subtracted from each timestamp to convert it to UTC used internally by Linux. This is useful when time zone set in ”…”�”}”(hjµh²hh³Nh´Nubj…)�”}”(hŒ ``sys_tz``”h]”hŒsys_tz”…”�”}”(hj½h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j„hjµubhŒÐ is not the time zone used by the filesystem. Note that this option still does not provide correct time stamps in all cases in presence of DST - time stamps in a different DST setting will be off by one hour.”…”�”}”(hjµh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K–hj²ubah}”(h]”h ]”h"]”h$]”h&]”uh1jKhj—ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j*h³hÊh´K�hj¤h²hubj+)�”}”(hŒ **showexec** If set, the execute permission bits of the file will be allowed only if the extension part of the name is .EXE, .COM, or .BAT. Not set by default. ”h]”(j1)�”}”(hŒ **showexec**”h]”j7)�”}”(hjçh]”hŒshowexec”…”�”}”(hjéh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hjåubah}”(h]”h ]”h"]”h$]”h&]”uh1j0h³hÊh´K¢hjáubjL)�”}”(hhh]”hÝ)�”}”(hŒ’If set, the execute permission bits of the file will be allowed only if the extension part of the name is .EXE, .COM, or .BAT. Not set by default.”h]”hŒ’If set, the execute permission bits of the file will be allowed only if the extension part of the name is .EXE, .COM, or .BAT. Not set by default.”…”�”}”(hjÿh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K hjüubah}”(h]”h ]”h"]”h$]”h&]”uh1jKhjáubeh}”(h]”h ]”h"]”h$]”h&]”uh1j*h³hÊh´K¢hj¤h²hubj+)�”}”(hŒ@**debug** Can be set, but unused by the current implementation. ”h]”(j1)�”}”(hŒ **debug**”h]”j7)�”}”(hjh]”hŒdebug”…”�”}”(hj!h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hjubah}”(h]”h ]”h"]”h$]”h&]”uh1j0h³hÊh´K¥hjubjL)�”}”(hhh]”hÝ)�”}”(hŒ5Can be set, but unused by the current implementation.”h]”hŒ5Can be set, but unused by the current implementation.”…”�”}”(hj7h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K¥hj4ubah}”(h]”h ]”h"]”h$]”h&]”uh1jKhjubeh}”(h]”h ]”h"]”h$]”h&]”uh1j*h³hÊh´K¥hj¤h²hubj+)�”}”(hŒo**sys_immutable** If set, ATTR_SYS attribute on FAT is handled as IMMUTABLE flag on Linux. Not set by default. ”h]”(j1)�”}”(hŒ**sys_immutable**”h]”j7)�”}”(hjWh]”hŒ sys_immutable”…”�”}”(hjYh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hjUubah}”(h]”h ]”h"]”h$]”h&]”uh1j0h³hÊh´K©hjQubjL)�”}”(hhh]”hÝ)�”}”(hŒ\If set, ATTR_SYS attribute on FAT is handled as IMMUTABLE flag on Linux. Not set by default.”h]”hŒ\If set, ATTR_SYS attribute on FAT is handled as IMMUTABLE flag on Linux. Not set by default.”…”�”}”(hjoh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K¨hjlubah}”(h]”h ]”h"]”h$]”h&]”uh1jKhjQubeh}”(h]”h ]”h"]”h$]”h&]”uh1j*h³hÊh´K©hj¤h²hubj+)�”}”(hŒg**flush** If set, the filesystem will try to flush to disk more early than normal. Not set by default. ”h]”(j1)�”}”(hŒ **flush**”h]”j7)�”}”(hj�h]”hŒflush”…”�”}”(hj‘h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hj�ubah}”(h]”h ]”h"]”h$]”h&]”uh1j0h³hÊh´K­hj‰ubjL)�”}”(hhh]”hÝ)�”}”(hŒ\If set, the filesystem will try to flush to disk more early than normal. Not set by default.”h]”hŒ\If set, the filesystem will try to flush to disk more early than normal. Not set by default.”…”�”}”(hj§h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K¬hj¤ubah}”(h]”h ]”h"]”h$]”h&]”uh1jKhj‰ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j*h³hÊh´K­hj¤h²hubj+)�”}”(hX!**rodir** FAT has the ATTR_RO (read-only) attribute. On Windows, the ATTR_RO of the directory will just be ignored, and is used only by applications as a flag (e.g. it's set for the customized folder). If you want to use ATTR_RO as read-only flag even for the directory, set this option. ”h]”(j1)�”}”(hŒ **rodir**”h]”j7)�”}”(hjÇh]”hŒrodir”…”�”}”(hjÉh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hjÅubah}”(h]”h ]”h"]”h$]”h&]”uh1j0h³hÊh´K¶hjÁubjL)�”}”(hhh]”(hÝ)�”}”(hŒ¿FAT has the ATTR_RO (read-only) attribute. On Windows, the ATTR_RO of the directory will just be ignored, and is used only by applications as a flag (e.g. it's set for the customized folder).”h]”hŒÁFAT has the ATTR_RO (read-only) attribute. On Windows, the ATTR_RO of the directory will just be ignored, and is used only by applications as a flag (e.g. it’s set for the customized folder).”…”�”}”(hjßh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K°hjÜubhÝ)�”}”(hŒUIf you want to use ATTR_RO as read-only flag even for the directory, set this option.”h]”hŒUIf you want to use ATTR_RO as read-only flag even for the directory, set this option.”…”�”}”(hjíh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KµhjÜubeh}”(h]”h ]”h"]”h$]”h&]”uh1jKhjÁubeh}”(h]”h ]”h"]”h$]”h&]”uh1j*h³hÊh´K¶hj¤h²hubj+)�”}”(hŒ´**errors=panic|continue|remount-ro** specify FAT behavior on critical errors: panic, continue without doing anything or remount the partition in read-only mode (default behavior). ”h]”(j1)�”}”(hŒ$**errors=panic|continue|remount-ro**”h]”j7)�”}”(hj h]”hŒ errors=panic|continue|remount-ro”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hj ubah}”(h]”h ]”h"]”h$]”h&]”uh1j0h³hÊh´K»hjubjL)�”}”(hhh]”hÝ)�”}”(hŒŽspecify FAT behavior on critical errors: panic, continue without doing anything or remount the partition in read-only mode (default behavior).”h]”hŒŽspecify FAT behavior on critical errors: panic, continue without doing anything or remount the partition in read-only mode (default behavior).”…”�”}”(hj%h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K¹hj"ubah}”(h]”h ]”h"]”h$]”h&]”uh1jKhjubeh}”(h]”h ]”h"]”h$]”h&]”uh1j*h³hÊh´K»hj¤h²hubj+)�”}”(hŒŸ**discard** If set, issues discard/TRIM commands to the block device when blocks are freed. This is useful for SSD devices and sparse/thinly-provisioned LUNs. ”h]”(j1)�”}”(hŒ **discard**”h]”j7)�”}”(hjEh]”hŒdiscard”…”�”}”(hjGh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hjCubah}”(h]”h ]”h"]”h$]”h&]”uh1j0h³hÊh´KÀhj?ubjL)�”}”(hhh]”hÝ)�”}”(hŒ’If set, issues discard/TRIM commands to the block device when blocks are freed. This is useful for SSD devices and sparse/thinly-provisioned LUNs.”h]”hŒ’If set, issues discard/TRIM commands to the block device when blocks are freed. This is useful for SSD devices and sparse/thinly-provisioned LUNs.”…”�”}”(hj]h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K¾hjZubah}”(h]”h ]”h"]”h$]”h&]”uh1jKhj?ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j*h³hÊh´KÀhj¤h²hubj+)�”}”(hX'**nfs=stale_rw|nostale_ro** Enable this only if you want to export the FAT filesystem over NFS. **stale_rw**: This option maintains an index (cache) of directory *inodes* by *i_logstart* which is used by the nfs-related code to improve look-ups. Full file operations (read/write) over NFS is supported but with cache eviction at NFS server, this could result in ESTALE issues. **nostale_ro**: This option bases the *inode* number and filehandle on the on-disk location of a file in the MS-DOS directory entry. This ensures that ESTALE will not be returned after a file is evicted from the inode cache. However, it means that operations such as rename, create and unlink could cause filehandles that previously pointed at one file to point at a different file, potentially causing data corruption. For this reason, this option also mounts the filesystem readonly. To maintain backward compatibility, ``'-o nfs'`` is also accepted, defaulting to "stale_rw". ”h]”(j1)�”}”(hŒ**nfs=stale_rw|nostale_ro**”h]”j7)�”}”(hj}h]”hŒnfs=stale_rw|nostale_ro”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hj{ubah}”(h]”h ]”h"]”h$]”h&]”uh1j0h³hÊh´KÖhjwubjL)�”}”(hhh]”(hÝ)�”}”(hŒCEnable this only if you want to export the FAT filesystem over NFS.”h]”hŒCEnable this only if you want to export the FAT filesystem over NFS.”…”�”}”(hj•h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÃhj’ubj‹)�”}”(hX**stale_rw**: This option maintains an index (cache) of directory *inodes* by *i_logstart* which is used by the nfs-related code to improve look-ups. Full file operations (read/write) over NFS is supported but with cache eviction at NFS server, this could result in ESTALE issues. **nostale_ro**: This option bases the *inode* number and filehandle on the on-disk location of a file in the MS-DOS directory entry. This ensures that ESTALE will not be returned after a file is evicted from the inode cache. However, it means that operations such as rename, create and unlink could cause filehandles that previously pointed at one file to point at a different file, potentially causing data corruption. For this reason, this option also mounts the filesystem readonly. ”h]”(hÝ)�”}”(hX**stale_rw**: This option maintains an index (cache) of directory *inodes* by *i_logstart* which is used by the nfs-related code to improve look-ups. Full file operations (read/write) over NFS is supported but with cache eviction at NFS server, this could result in ESTALE issues.”h]”(j7)�”}”(hŒ **stale_rw**”h]”hŒstale_rw”…”�”}”(hj«h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hj§ubhŒ6: This option maintains an index (cache) of directory ”…”�”}”(hj§h²hh³Nh´NubjÉ)�”}”(hŒ*inodes*”h]”hŒinodes”…”�”}”(hj½h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÈhj§ubhŒ by ”…”�”}”(hj§h²hh³Nh´NubjÉ)�”}”(hŒ *i_logstart*”h]”hŒ i_logstart”…”�”}”(hjÏh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÈhj§ubhŒ¾ which is used by the nfs-related code to improve look-ups. Full file operations (read/write) over NFS is supported but with cache eviction at NFS server, this could result in ESTALE issues.”…”�”}”(hj§h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÆhj£ubhÝ)�”}”(hXå**nostale_ro**: This option bases the *inode* number and filehandle on the on-disk location of a file in the MS-DOS directory entry. This ensures that ESTALE will not be returned after a file is evicted from the inode cache. However, it means that operations such as rename, create and unlink could cause filehandles that previously pointed at one file to point at a different file, potentially causing data corruption. For this reason, this option also mounts the filesystem readonly.”h]”(j7)�”}”(hŒ**nostale_ro**”h]”hŒ nostale_ro”…”�”}”(hjëh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hjçubhŒ: This option bases the ”…”�”}”(hjçh²hh³Nh´NubjÉ)�”}”(hŒ*inode*”h]”hŒinode”…”�”}”(hjýh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÈhjçubhX¸ number and filehandle on the on-disk location of a file in the MS-DOS directory entry. This ensures that ESTALE will not be returned after a file is evicted from the inode cache. However, it means that operations such as rename, create and unlink could cause filehandles that previously pointed at one file to point at a different file, potentially causing data corruption. For this reason, this option also mounts the filesystem readonly.”…”�”}”(hjçh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÌhj£ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jŠh³hÊh´KÆhj’ubhÝ)�”}”(hŒ\To maintain backward compatibility, ``'-o nfs'`` is also accepted, defaulting to "stale_rw".”h]”(hŒ$To maintain backward compatibility, ”…”�”}”(hj h²hh³Nh´Nubj…)�”}”(hŒ ``'-o nfs'``”h]”hŒ'-o nfs'”…”�”}”(hj# h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j„hj ubhŒ0 is also accepted, defaulting to “stale_rwâ€�.”…”�”}”(hj h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÕhj’ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jKhjwubeh}”(h]”h ]”h"]”h$]”h&]”uh1j*h³hÊh´KÖhj¤h²hubj+)�”}”(hX**dos1xfloppy : 0,1,yes,no,true,false** If set, use a fallback default BIOS Parameter Block configuration, determined by backing device size. These static parameters match defaults assumed by DOS 1.x for 160 kiB, 180 kiB, 320 kiB, and 360 kiB floppies and floppy images. ”h]”(j1)�”}”(hŒ.**dos1xfloppy : 0,1,yes,no,true,false**”h]”j7)�”}”(hjM h]”hŒ*dos1xfloppy : 0,1,yes,no,true,false”…”�”}”(hjO h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j6hjK ubah}”(h]”h ]”h"]”h$]”h&]”uh1j0h³hÊh´KÞhjG ubjL)�”}”(hhh]”hÝ)�”}”(hŒæIf set, use a fallback default BIOS Parameter Block configuration, determined by backing device size. These static parameters match defaults assumed by DOS 1.x for 160 kiB, 180 kiB, 320 kiB, and 360 kiB floppies and floppy images.”h]”hŒæIf set, use a fallback default BIOS Parameter Block configuration, determined by backing device size. These static parameters match defaults assumed by DOS 1.x for 160 kiB, 180 kiB, 320 kiB, and 360 kiB floppies and floppy images.”…”�”}”(hje h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÙhjb ubah}”(h]”h ]”h"]”h$]”h&]”uh1jKhjG ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j*h³hÊh´KÞhj¤h²hubeh}”(h]”h ]”h"]”h$]”h&]”uh1j%hjh²hh³hÊh´Nubeh}”(h]”Œvfat-mount-options”ah ]”h"]”Œvfat mount options”ah$]”h&]”uh1hµhh·h²hh³hÊh´Kubh¶)�”}”(hhh]”(h»)�”}”(hŒ LIMITATION”h]”hŒ LIMITATION”…”�”}”(hj� h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj� h²hh³hÊh´KáubhÝ)�”}”(hXŠThe fallocated region of file is discarded at umount/evict time when using fallocate with FALLOC_FL_KEEP_SIZE. So, User should assume that fallocated region can be discarded at last close if there is memory pressure resulting in eviction of the inode from the memory. As a result, for any dependency on the fallocated region, user should make sure to recheck fallocate after reopening the file.”h]”hXŠThe fallocated region of file is discarded at umount/evict time when using fallocate with FALLOC_FL_KEEP_SIZE. So, User should assume that fallocated region can be discarded at last close if there is memory pressure resulting in eviction of the inode from the memory. As a result, for any dependency on the fallocated region, user should make sure to recheck fallocate after reopening the file.”…”�”}”(hjž h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Kãhj� h²hubeh}”(h]”Œ limitation”ah ]”h"]”Œ limitation”ah$]”h&]”uh1hµhh·h²hh³hÊh´Káubh¶)�”}”(hhh]”(h»)�”}”(hŒTODO”h]”hŒTODO”…”�”}”(hj· h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj´ h²hh³hÊh´KìubhÝ)�”}”(hŒ°Need to get rid of the raw scanning stuff. Instead, always use a get next directory entry approach. The only thing left that uses raw scanning is the directory renaming code.”h]”hŒ°Need to get rid of the raw scanning stuff. Instead, always use a get next directory entry approach. The only thing left that uses raw scanning is the directory renaming code.”…”�”}”(hjÅ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Kíhj´ h²hubeh}”(h]”Œtodo”ah ]”h"]”Œtodo”ah$]”h&]”uh1hµhh·h²hh³hÊh´Kìubh¶)�”}”(hhh]”(h»)�”}”(hŒPOSSIBLE PROBLEMS”h]”hŒPOSSIBLE PROBLEMS”…”�”}”(hjÞ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjÛ h²hh³hÊh´KóubhŒ bullet_list”“”)�”}”(hhh]”(hŒ list_item”“”)�”}”(hŒ=vfat_valid_longname does not properly checked reserved names.”h]”hÝ)�”}”(hjõ h]”hŒ=vfat_valid_longname does not properly checked reserved names.”…”�”}”(hj÷ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Kõhjó ubah}”(h]”h ]”h"]”h$]”h&]”uh1jñ hjî h²hh³hÊh´Nubjò )�”}”(hŒ“When a volume name is the same as a directory name in the root directory of the filesystem, the directory name sometimes shows up as an empty file.”h]”hÝ)�”}”(hŒ“When a volume name is the same as a directory name in the root directory of the filesystem, the directory name sometimes shows up as an empty file.”h]”hŒ“When a volume name is the same as a directory name in the root directory of the filesystem, the directory name sometimes shows up as an empty file.”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Köhj ubah}”(h]”h ]”h"]”h$]”h&]”uh1jñ hjî h²hh³hÊh´Nubjò )�”}”(hŒ*autoconv option does not work correctly. ”h]”hÝ)�”}”(hŒ(autoconv option does not work correctly.”h]”hŒ(autoconv option does not work correctly.”…”�”}”(hj& h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Kùhj" ubah}”(h]”h ]”h"]”h$]”h&]”uh1jñ hjî h²hh³hÊh´Nubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1jì h³hÊh´KõhjÛ h²hubeh}”(h]”Œpossible-problems”ah ]”h"]”Œpossible problems”ah$]”h&]”uh1hµhh·h²hh³hÊh´Kóubh¶)�”}”(hhh]”(h»)�”}”(hŒ TEST SUITE”h]”hŒ TEST SUITE”…”�”}”(hjM h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjJ h²hh³hÊh´KýubhÝ)�”}”(hŒ€If you plan to make any modifications to the vfat filesystem, please get the test suite that comes with the vfat distribution at”h]”hŒ€If you plan to make any modifications to the vfat filesystem, please get the test suite that comes with the vfat distribution at”…”�”}”(hj[ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KþhjJ h²hubhÝ)�”}”(hŒS``_”h]”(hŒ reference”“”)�”}”(hjk h]”hŒNhttp://web.archive.org/web/*/http://bmrc.berkeley.edu/people/chaffee/vfat.html”…”�”}”(hjo h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒNhttp://web.archive.org/web/*/http://bmrc.berkeley.edu/people/chaffee/vfat.html”Œrefuri”j} uh1jm hji ubhŒtarget”“”)�”}”(hŒP”h]”h}”(h]”ŒHhttp-web-archive-org-web-http-bmrc-berkeley-edu-people-chaffee-vfat-html”ah ]”h"]”ŒNhttp://web.archive.org/web/*/http://bmrc.berkeley.edu/people/chaffee/vfat.html”ah$]”h&]”Œrefuri”j} uh1j Œ referenced”Khji ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MhjJ h²hubhÝ)�”}”(hŒ„This tests quite a few parts of the vfat filesystem and additional tests for new features or untested features would be appreciated.”h]”hŒ„This tests quite a few parts of the vfat filesystem and additional tests for new features or untested features would be appreciated.”…”�”}”(hj• h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MhjJ h²hubeh}”(h]”Œ test-suite”ah ]”h"]”Œ test suite”ah$]”h&]”uh1hµhh·h²hh³hÊh´Kýubh¶)�”}”(hhh]”(h»)�”}”(hŒ-NOTES ON THE STRUCTURE OF THE VFAT FILESYSTEM”h]”hŒ-NOTES ON THE STRUCTURE OF THE VFAT FILESYSTEM”…”�”}”(hj® h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj« h²hh³hÊh´MubhÝ)�”}”(hŒqThis documentation was provided by Galen C. Hunt gchunt@cs.rochester.edu and lightly annotated by Gordon Chaffee.”h]”(hŒ1This documentation was provided by Galen C. Hunt ”…”�”}”(hj¼ h²hh³Nh´Nubjn )�”}”(hŒgchunt@cs.rochester.edu”h]”hŒgchunt@cs.rochester.edu”…”�”}”(hjÄ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:gchunt@cs.rochester.edu”uh1jm hj¼ ubhŒ) and lightly annotated by Gordon Chaffee.”…”�”}”(hj¼ h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mhj« h²hubhÝ)�”}”(hŒàThis document presents a very rough, technical overview of my knowledge of the extended FAT file system used in Windows NT 3.5 and Windows 95. I don't guarantee that any of the following is correct, but it appears to be so.”h]”hŒâThis document presents a very rough, technical overview of my knowledge of the extended FAT file system used in Windows NT 3.5 and Windows 95. I don’t guarantee that any of the following is correct, but it appears to be so.”…”�”}”(hjÞ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M hj« h²hubhÝ)�”}”(hXKThe extended FAT file system is almost identical to the FAT file system used in DOS versions up to and including *6.223410239847* :-). The significant change has been the addition of long file names. These names support up to 255 characters including spaces and lower case characters as opposed to the traditional 8.3 short names.”h]”(hŒqThe extended FAT file system is almost identical to the FAT file system used in DOS versions up to and including ”…”�”}”(hjì h²hh³Nh´NubjÉ)�”}”(hŒ*6.223410239847*”h]”hŒ6.223410239847”…”�”}”(hjô h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÈhjì ubhŒÊ :-). The significant change has been the addition of long file names. These names support up to 255 characters including spaces and lower case characters as opposed to the traditional 8.3 short names.”…”�”}”(hjì h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mhj« h²hubhÝ)�”}”(hŒ[Here is the description of the traditional FAT entry in the current Windows 95 filesystem::”h]”hŒZHere is the description of the traditional FAT entry in the current Windows 95 filesystem:”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mhj« h²hubhí)�”}”(hX=struct directory { // Short 8.3 names unsigned char name[8]; // file name unsigned char ext[3]; // file extension unsigned char attr; // attribute byte unsigned char lcase; // Case for base and extension unsigned char ctime_ms; // Creation time, milliseconds unsigned char ctime[2]; // Creation time unsigned char cdate[2]; // Creation date unsigned char adate[2]; // Last access date unsigned char reserved[2]; // reserved values (ignored) unsigned char time[2]; // time stamp unsigned char date[2]; // date stamp unsigned char start[2]; // starting cluster number unsigned char size[4]; // size of the file };”h]”hX=struct directory { // Short 8.3 names unsigned char name[8]; // file name unsigned char ext[3]; // file extension unsigned char attr; // attribute byte unsigned char lcase; // Case for base and extension unsigned char ctime_ms; // Creation time, milliseconds unsigned char ctime[2]; // Creation time unsigned char cdate[2]; // Creation date unsigned char adate[2]; // Last access date unsigned char reserved[2]; // reserved values (ignored) unsigned char time[2]; // time stamp unsigned char date[2]; // date stamp unsigned char start[2]; // starting cluster number unsigned char size[4]; // size of the file };”…”�”}”hj sbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´Mhj« h²hubhÝ)�”}”(hXÈThe lcase field specifies if the base and/or the extension of an 8.3 name should be capitalized. This field does not seem to be used by Windows 95 but it is used by Windows NT. The case of filenames is not completely compatible from Windows NT to Windows 95. It is not completely compatible in the reverse direction, however. Filenames that fit in the 8.3 namespace and are written on Windows NT to be lowercase will show up as uppercase on Windows 95.”h]”hXÈThe lcase field specifies if the base and/or the extension of an 8.3 name should be capitalized. This field does not seem to be used by Windows 95 but it is used by Windows NT. The case of filenames is not completely compatible from Windows NT to Windows 95. It is not completely compatible in the reverse direction, however. Filenames that fit in the 8.3 namespace and are written on Windows NT to be lowercase will show up as uppercase on Windows 95.”…”�”}”(hj( h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M*hj« h²hubj{)�”}”(hŒ¹Note that the ``start`` and ``size`` values are actually little endian integer values. The descriptions of the fields in this structure are public knowledge and can be found elsewhere.”h]”hÝ)�”}”(hŒ¹Note that the ``start`` and ``size`` values are actually little endian integer values. The descriptions of the fields in this structure are public knowledge and can be found elsewhere.”h]”(hŒNote that the ”…”�”}”(hj: h²hh³Nh´Nubj…)�”}”(hŒ ``start``”h]”hŒstart”…”�”}”(hjB h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j„hj: ubhŒ and ”…”�”}”(hj: h²hh³Nh´Nubj…)�”}”(hŒ``size``”h]”hŒsize”…”�”}”(hjT h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j„hj: ubhŒ• values are actually little endian integer values. The descriptions of the fields in this structure are public knowledge and can be found elsewhere.”…”�”}”(hj: h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M2hj6 ubah}”(h]”h ]”h"]”h$]”h&]”uh1jzhj« h²hh³hÊh´NubhÝ)�”}”(hXLWith the extended FAT system, Microsoft has inserted extra directory entries for any files with extended names. (Any name which legally fits within the old 8.3 encoding scheme does not have extra entries.) I call these extra entries slots. Basically, a slot is a specially formatted directory entry which holds up to 13 characters of a file's extended name. Think of slots as additional labeling for the directory entry of the file to which they correspond. Microsoft prefers to refer to the 8.3 entry for a file as its alias and the extended slot directory entries as the file name.”h]”hXNWith the extended FAT system, Microsoft has inserted extra directory entries for any files with extended names. (Any name which legally fits within the old 8.3 encoding scheme does not have extra entries.) I call these extra entries slots. Basically, a slot is a specially formatted directory entry which holds up to 13 characters of a file’s extended name. Think of slots as additional labeling for the directory entry of the file to which they correspond. Microsoft prefers to refer to the 8.3 entry for a file as its alias and the extended slot directory entries as the file name.”…”�”}”(hjr h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M6hj« h²hubhÝ)�”}”(hŒ4The C structure for a slot directory entry follows::”h]”hŒ3The C structure for a slot directory entry follows:”…”�”}”(hj€ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M@hj« h²hubhí)�”}”(hX=struct slot { // Up to 13 characters of a long name unsigned char id; // sequence number for slot unsigned char name0_4[10]; // first 5 characters in name unsigned char attr; // attribute byte unsigned char reserved; // always 0 unsigned char alias_checksum; // checksum for 8.3 alias unsigned char name5_10[12]; // 6 more characters in name unsigned char start[2]; // starting cluster number unsigned char name11_12[4]; // last 2 characters in name };”h]”hX=struct slot { // Up to 13 characters of a long name unsigned char id; // sequence number for slot unsigned char name0_4[10]; // first 5 characters in name unsigned char attr; // attribute byte unsigned char reserved; // always 0 unsigned char alias_checksum; // checksum for 8.3 alias unsigned char name5_10[12]; // 6 more characters in name unsigned char start[2]; // starting cluster number unsigned char name11_12[4]; // last 2 characters in name };”…”�”}”hjŽ sbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´MBhj« h²hubhÝ)�”}”(hŒ÷If the layout of the slots looks a little odd, it's only because of Microsoft's efforts to maintain compatibility with old software. The slots must be disguised to prevent old software from panicking. To this end, a number of measures are taken:”h]”hŒûIf the layout of the slots looks a little odd, it’s only because of Microsoft’s efforts to maintain compatibility with old software. The slots must be disguised to prevent old software from panicking. To this end, a number of measures are taken:”…”�”}”(hjœ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MNhj« h²hubj‹)�”}”(hXµ1) The attribute byte for a slot directory entry is always set to 0x0f. This corresponds to an old directory entry with attributes of "hidden", "system", "read-only", and "volume label". Most old software will ignore any directory entries with the "volume label" bit set. Real volume label entries don't have the other three bits set. 2) The starting cluster is always set to 0, an impossible value for a DOS file. ”h]”hŒenumerated_list”“”)�”}”(hhh]”(jò )�”}”(hXOThe attribute byte for a slot directory entry is always set to 0x0f. This corresponds to an old directory entry with attributes of "hidden", "system", "read-only", and "volume label". Most old software will ignore any directory entries with the "volume label" bit set. Real volume label entries don't have the other three bits set. ”h]”hÝ)�”}”(hXNThe attribute byte for a slot directory entry is always set to 0x0f. This corresponds to an old directory entry with attributes of "hidden", "system", "read-only", and "volume label". Most old software will ignore any directory entries with the "volume label" bit set. Real volume label entries don't have the other three bits set.”h]”hXdThe attribute byte for a slot directory entry is always set to 0x0f. This corresponds to an old directory entry with attributes of “hiddenâ€�, “systemâ€�, “read-onlyâ€�, and “volume labelâ€�. Most old software will ignore any directory entries with the “volume labelâ€� bit set. Real volume label entries don’t have the other three bits set.”…”�”}”(hj· h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MShj³ ubah}”(h]”h ]”h"]”h$]”h&]”uh1jñ hj° ubjò )�”}”(hŒMThe starting cluster is always set to 0, an impossible value for a DOS file. ”h]”hÝ)�”}”(hŒLThe starting cluster is always set to 0, an impossible value for a DOS file.”h]”hŒLThe starting cluster is always set to 0, an impossible value for a DOS file.”…”�”}”(hjÏ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MZhjË ubah}”(h]”h ]”h"]”h$]”h&]”uh1jñ hj° ubeh}”(h]”h ]”h"]”h$]”h&]”Œenumtype”Œarabic”Œprefix”hŒsuffix”Œ)”uh1j® hjª ubah}”(h]”h ]”h"]”h$]”h&]”uh1jŠh³hÊh´MShj« h²hubhÝ)�”}”(hXBecause the extended FAT system is backward compatible, it is possible for old software to modify directory entries. Measures must be taken to ensure the validity of slots. An extended FAT system can verify that a slot does in fact belong to an 8.3 directory entry by the following:”h]”hXBecause the extended FAT system is backward compatible, it is possible for old software to modify directory entries. Measures must be taken to ensure the validity of slots. An extended FAT system can verify that a slot does in fact belong to an 8.3 directory entry by the following:”…”�”}”(hjô h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M]hj« h²hubj‹)�”}”(hXÜ1) Positioning. Slots for a file always immediately proceed their corresponding 8.3 directory entry. In addition, each slot has an id which marks its order in the extended file name. Here is a very abbreviated view of an 8.3 directory entry and its corresponding long name slots for the file "My Big File.Extension which is long":: .. note:: Note that the slots are stored from last to first. Slots are numbered from 1 to N. The Nth slot is ``or'ed`` with 0x40 to mark it as the last one. 2) Checksum. Each slot has an alias_checksum value. The checksum is calculated from the 8.3 name using the following algorithm:: for (sum = i = 0; i < 11; i++) { sum = (((sum&1)<<7)|((sum&0xfe)>>1)) + name[i] } 3) If there is free space in the final slot, a Unicode ``NULL (0x0000)`` is stored after the final character. After that, all unused characters in the final slot are set to Unicode 0xFFFF. ”h]”j¯ )�”}”(hhh]”(jò )�”}”(hXïPositioning. Slots for a file always immediately proceed their corresponding 8.3 directory entry. In addition, each slot has an id which marks its order in the extended file name. Here is a very abbreviated view of an 8.3 directory entry and its corresponding long name slots for the file "My Big File.Extension which is long":: .. note:: Note that the slots are stored from last to first. Slots are numbered from 1 to N. The Nth slot is ``or'ed`` with 0x40 to mark it as the last one. ”h]”(hÝ)�”}”(hXKPositioning. Slots for a file always immediately proceed their corresponding 8.3 directory entry. In addition, each slot has an id which marks its order in the extended file name. Here is a very abbreviated view of an 8.3 directory entry and its corresponding long name slots for the file "My Big File.Extension which is long"::”h]”hXNPositioning. Slots for a file always immediately proceed their corresponding 8.3 directory entry. In addition, each slot has an id which marks its order in the extended file name. Here is a very abbreviated view of an 8.3 directory entry and its corresponding long name slots for the file “My Big File.Extension which is longâ€�:”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mchj ubhí)�”}”(hŒÓ ”h]”hŒÓ ”…”�”}”hj sbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´Mjhj ubj{)�”}”(hŒ”Note that the slots are stored from last to first. Slots are numbered from 1 to N. The Nth slot is ``or'ed`` with 0x40 to mark it as the last one.”h]”hÝ)�”}”(hŒ”Note that the slots are stored from last to first. Slots are numbered from 1 to N. The Nth slot is ``or'ed`` with 0x40 to mark it as the last one.”h]”(hŒeNote that the slots are stored from last to first. Slots are numbered from 1 to N. The Nth slot is ”…”�”}”(hj- h²hh³Nh´Nubj…)�”}”(hŒ ``or'ed``”h]”hŒor'ed”…”�”}”(hj5 h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j„hj- ubhŒ& with 0x40 to mark it as the last one.”…”�”}”(hj- h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mqhj) ubah}”(h]”h ]”h"]”h$]”h&]”uh1jzhj ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jñ hj ubjò )�”}”(hŒëChecksum. Each slot has an alias_checksum value. The checksum is calculated from the 8.3 name using the following algorithm:: for (sum = i = 0; i < 11; i++) { sum = (((sum&1)<<7)|((sum&0xfe)>>1)) + name[i] } ”h]”(hÝ)�”}”(hŒChecksum. Each slot has an alias_checksum value. The checksum is calculated from the 8.3 name using the following algorithm::”h]”hŒ~Checksum. Each slot has an alias_checksum value. The checksum is calculated from the 8.3 name using the following algorithm:”…”�”}”(hj] h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MuhjY ubhí)�”}”(hŒYfor (sum = i = 0; i < 11; i++) { sum = (((sum&1)<<7)|((sum&0xfe)>>1)) + name[i] }”h]”hŒYfor (sum = i = 0; i < 11; i++) { sum = (((sum&1)<<7)|((sum&0xfe)>>1)) + name[i] }”…”�”}”hjk sbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´MyhjY ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jñ hj ubjò )�”}”(hŒ»If there is free space in the final slot, a Unicode ``NULL (0x0000)`` is stored after the final character. After that, all unused characters in the final slot are set to Unicode 0xFFFF. ”h]”hÝ)�”}”(hŒºIf there is free space in the final slot, a Unicode ``NULL (0x0000)`` is stored after the final character. After that, all unused characters in the final slot are set to Unicode 0xFFFF.”h]”(hŒ4If there is free space in the final slot, a Unicode ”…”�”}”(hjƒ h²hh³Nh´Nubj…)�”}”(hŒ``NULL (0x0000)``”h]”hŒ NULL (0x0000)”…”�”}”(hj‹ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j„hjƒ ubhŒu is stored after the final character. After that, all unused characters in the final slot are set to Unicode 0xFFFF.”…”�”}”(hjƒ h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M~hj ubah}”(h]”h ]”h"]”h$]”h&]”uh1jñ hj ubeh}”(h]”h ]”h"]”h$]”h&]”jé jê jë hjì jí uh1j® hj ubah}”(h]”h ]”h"]”h$]”h&]”uh1jŠh³hÊh´Mchj« h²hubhÝ)�”}”(hŒ„Finally, note that the extended name is stored in Unicode. Each Unicode character takes either two or four bytes, UTF-16LE encoded.”h]”hŒ„Finally, note that the extended name is stored in Unicode. Each Unicode character takes either two or four bytes, UTF-16LE encoded.”…”�”}”(hjµ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M‚hj« h²hubeh}”(h]”Œ-notes-on-the-structure-of-the-vfat-filesystem”ah ]”h"]”Œ-notes on the structure of the vfat filesystem”ah$]”h&]”uh1hµhh·h²hh³hÊh´Mubeh}”(h]”Œvfat”ah ]”h"]”Œvfat”ah$]”h&]”uh1hµhhh²hh³hÊh´Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”hÊuh1hŒcurrent_source”NŒ current_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)�”}”(hºNŒ generator”NŒ datestamp”NŒ source_link”NŒ source_url”NŒ toc_backlinks”Œentry”Œfootnote_backlinks”KŒ sectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒ strip_classes”NŒ report_level”KŒ halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ traceback”ˆŒinput_encoding”Œ utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”jö Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œ language_code”Œen”Œrecord_dependencies”NŒconfig”NŒ id_prefix”hŒauto_id_prefix”Œid”Œ dump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”hÊŒ _destination”NŒ _config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒ raw_enabled”KŒline_length_limit”M'Œpep_references”NŒ pep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒ rfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œ smart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œ docinfo_xform”KŒsectsubtitle_xform”‰Œ image_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”•‹}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(jÐ jÍ jjjŠ j‡ j± j® jØ jÕ jG jD j¨ j¥ jŠ j‡ jÈ jÅ uŒ nametypes”}”(jÐ ‰j‰jŠ ‰j± ‰jØ ‰jG ‰j¨ ‰jŠ ˆjÈ ‰uh}”(jÍ h·jhËj‡ jj® j� jÕ j´ jD jÛ j¥ jJ j‡ j� jÅ j« uŒ footnote_refs”}”Œ citation_refs”}”Œ autofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ footnotes”]”Œ citations”]”Œautofootnote_start”KŒsymbol_footnote_start”KŒ id_counter”Œ collections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œ transformer”NŒ include_log”]”Œ decoration”Nh²hub.