FAT filesystem and Linux: Difference between revisions

Revision as of 00:15, 30 June 2023

Revision as of 00:20, 30 June 2023

Line 34:

== Commonalities ==

As mentioned previously, all of the Linux filesystem drivers support all of the three File Allocation Table sizes, 12-bit, 16-bit, and 32-bit. Other common features that they all support are various Linux mounting options (specified with the <code>-o</code> option to the <code>[[mount (Unix)|mount]]</code> command):<ref name="Smith1"/><ref name="Smith2"/>

;<code>uid</code> and <code>gid</code>:These two options tell the filesystem driver to set the (default, in the case of ''{{Not a typo|umsdos}}'') owner user ID and group ID to be a single, specified, value for all files in the volume. Both IDs are specified as numeric values (as to be found in the <code>[[/etc/passwd]]</code> file). So, for example, to specify to the ''{{Not a typo|vfat}}'' filesystem driver that all files and directories are to have owner ID 745 and group ID 15, the <code>mount</code> command would be invoked as <syntaxhighlight lang{{nowrap|1="bash" inline<code>mount -t vfat -o uid=745,gid=15</syntaxhighlightcode>.<ref name="Smith1"/><ref name="Smith2"/>}} Linux filesystem drivers do not at present incorporate support for [[FAT file password|file/directory password]]s on FAT12/FAT16/FAT32 volumes and multi-user [[FAT file access rights|world/group/owner access permissions for read/write/delete/execute rights]] on FAT12/FAT16 volumes as implemented in various operating systems of the Digital Research family, including [[DR-DOS]], [[PalmDOS]], [[Novell DOS]], [[OpenDOS]], [[FlexOS]], [[Concurrent DOS]], [[Multiuser DOS]], System Manager and [[REAL/32]].<!-- not sure if REAL/32 supports owner-IDs on FAT32. If it does it would require certain tweaks as the owner-ID entry is used for the high-word of the cluster number on FAT32 volumes now -->

;<code>umask</code>:This option sets the [[umask]] to apply globally to all files in the volume. For example, to specify to the ''{{Not a typo|vfat}}'' filesystem driver that no "group" or "other" access is to be allowed, the <code>mount</code> command would be invoked as {{nowrap|1=<syntaxhighlight lang="bash"code inline>mount -t vfat -o umask=077</syntaxhighlightcode>.<ref name="Smith1"/><ref name="Smith2"/>}}

;<code>conv</code>:This option specifies ''file content conversion'' semantics. It is possible for the filesystem drivers to convert the newline conventions in files, between LF termination and CRLF termination, on the fly as files are read and written. By default this conversion is entirely disabled. The filesystem drivers can perform conversion for some files, attempting to auto-detect what files to convert based upon the extension portion of the filename, or globally for all files. These three conversion levels are specified as <code>conv=b</code> (for "binary"), <code>conv=a</code> (for "auto-detect"), and <code>conv=t</code> (for "text"), respectively. The latter two options carry an inherent risk of corrupting non-text file data. No conversion at all is the default.<ref name="Smith1"/><ref name="Smith2"/>