Content deleted Content added
Cyberbot II (talk | contribs) Tagging page with {{Blacklisted-links}}. Blacklisted links found. (Peachy 2.0 (alpha 8)) |
m clean up, typo(s) fixed: Therefore → Therefore, (2) using AWB |
||
Line 11:
=== umsdos ===
The key advantage to ''umsdos'' out of the three is that it provides full Unix file semantics. Therefore, it can be used in situations where it is desirable to install Linux on and run it from a FAT disk volume, which require such semantics to be available. However, Linux installed on and running from such a disk volume is slower than Linux installed on and running from a disk volume formatted with, for example, the [[ext2]] filesystem format.<ref name=StanfieldSmith /><ref name=StroberElling>{{cite book|title=Linux, unleashing the workstation in your PC|series=The Complete Linux Kit, Rainer Maurer|author=Stefan Strobel and Volker Elling|edition=3rd|publisher=Springer|year=1997|isbn=978-0-387-94880-5|pages=43}}</ref> Further, unless a utility program is regularly run every time that one switches from running Windows to running Linux, certain changes made to files and directories on the disk by Windows will cause error messages about inaccessible files in Linux.<ref name=McCune>{{cite book|title=Integrating Linux and Windows|series=Open source technology series|author=Mike McCune|publisher=Prentice Hall PTR|year=2001|isbn= 978-0-13-030670-8|pages=7–9}}</ref>
=== vfat ===
Line 38:
In the absence of this file in any given directory, and thus by default, the ''umsdos'' filesystem driver provides the same semantics as the ''msdos'' filesystem driver does for the directory: only 8.3 filenames and no extra Unix file semantics. To enable the ''umsdos'' driver's extra abilities, it is necessary to create that file in the directory and synchronize its internal data with the normal FAT data for any existing entries already in the directory. This is done with a tool called <tt>umssync</tt>.<ref name=StanfieldSmith /><ref name=Smith1 /><ref name=McCune />
This is the utility program that is run, across every directory on the disc volume, every time that one switches from running Windows to running Linux, in order for the ''umsdos'' filesystem driver to incorporate any changes made to files and directories by Windows into its private data structures in its <tt>--LINUX-.---</tt> file. By default, the <tt>umssync</tt> tool creates <tt>--LINUX-.---</tt> files in directories if they do not already exist, resulting in such a file in every directory in the disc volume. When switching between Windows and Linux this behaviour is not often considered desirable. Therefore, the normal mode of operation when invoking <tt>umssync</tt> after switching from Windows to Linux (which is usually done by running the tool at Linux boot time from a startup script) is to employ the <tt>-c</tt> option to the command, which prevents the creation of any new <tt>--LINUX-.---</tt> files in directories that do not already possess them.<ref name=StanfieldSmith /><ref name=Smith1 /><ref name=McCune />
== Installing Linux on and booting it from FAT volumes using umsdos ==
| |||