From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: [PATCH] FAT: update document
Date: Thu, 08 Jul 2004 04:24:07 +0900 [thread overview]
Message-ID: <87d637mxig.fsf@devron.myhome.or.jp> (raw)
Signed-off-by: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
---
Documentation/filesystems/vfat.txt | 32 +++++++++++++++++++++++---------
fs/Kconfig | 15 +++++++++------
2 files changed, 32 insertions(+), 15 deletions(-)
diff -puN Documentation/filesystems/vfat.txt~fat_doc-update Documentation/filesystems/vfat.txt
--- linux-2.6.7/Documentation/filesystems/vfat.txt~fat_doc-update 2004-07-04 02:37:33.000000000 +0900
+++ linux-2.6.7-hirofumi/Documentation/filesystems/vfat.txt 2004-07-05 03:32:52.000000000 +0900
@@ -10,23 +10,35 @@ VFAT MOUNT OPTIONS
----------------------------------------------------------------------
umask=### -- The permission mask (for files and directories, see umask(1)).
The default is the umask of current process.
+
dmask=### -- The permission mask for the directory.
The default is the umask of current process.
+
fmask=### -- The permission mask for files.
The default is the umask of current process.
-codepage=### -- Sets the codepage for converting to shortname characters
- on FAT and VFAT filesystems. By default, codepage 437
- is used. This is the default for the U.S. and some
- European countries.
-iocharset=name -- Character set to use for converting between 8 bit characters
- 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. There is also an option of
- doing UTF8 translations with the utf8 option.
+
+codepage=### -- Sets the codepage number for converting to shortname
+ characters on FAT filesystem.
+ By default, FAT_DEFAULT_CODEPAGE setting is used.
+
+iocharset=name -- 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 UTF8 translations
+ with the utf8 option.
+
+ NOTE: "iocharset=utf8" is not recommended. If unsure,
+ you should consider the following option instead.
+
utf8=<bool> -- UTF8 is the filesystem safe version of Unicode that
is used by the console. It can be be enabled for the
filesystem with this option. If 'uni_xlate' gets set,
UTF8 gets disabled.
+
uni_xlate=<bool> -- Translate unhandled Unicode characters to special
escaped sequences. This would let you backup and
restore filenames that are created with any Unicode
@@ -37,6 +49,7 @@ uni_xlate=<bool> -- Translate unhandled
illegal on the vfat filesystem. The escape sequence
that gets used is ':' and the four digits of hexadecimal
unicode.
+
nonumtail=<bool> -- 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
@@ -45,6 +58,7 @@ nonumtail=<bool> -- When creating 8.3 al
be the short alias instead of 'longfi~1.txt'.
quiet -- Stops printing certain warning messages.
+
check=s|r|n -- Case sensitivity checking setting.
s: strict, case sensitive
r: relaxed, case insensitive
diff -puN fs/Kconfig~fat_doc-update fs/Kconfig
--- linux-2.6.7/fs/Kconfig~fat_doc-update 2004-07-04 02:37:33.000000000 +0900
+++ linux-2.6.7-hirofumi/fs/Kconfig 2004-07-05 04:31:56.000000000 +0900
@@ -678,18 +678,21 @@ config FAT_DEFAULT_CODEPAGE
default 437
help
This option should be set to the codepage of your FAT filesystems.
- It can be overridden with the 'codepage' mount option.
+ It can be overridden with the "codepage" mount option.
+ See <file:Documentation/filesystems/vfat.txt> for more information.
config FAT_DEFAULT_IOCHARSET
string "Default iocharset for FAT"
depends on VFAT_FS
default "iso8859-1"
help
- Set this to the default I/O character set you'd like FAT to use.
- It should probably match the character set that most of your
- FAT filesystems use, and can be overridded with the 'iocharset'
- mount option for FAT filesystems. Note that UTF8 is *not* a
- supported charset for FAT filesystems.
+ Set this to the default input/output character set you'd
+ like FAT to use. It should probably match the character set
+ that most of your FAT filesystems use, and can be overrided
+ with the "iocharset" mount option for FAT filesystems.
+ Note that "utf8" is not recommended for FAT filesystems.
+ If unsure, you shouldn't set "utf8" to here.
+ See <file:Documentation/filesystems/vfat.txt> for more information.
config UMSDOS_FS
#dep_tristate ' UMSDOS: Unix-like file system on top of standard MSDOS fs' CONFIG_UMSDOS_FS $CONFIG_MSDOS_FS
_
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next reply other threads:[~2004-07-07 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-07 19:24 OGAWA Hirofumi [this message]
2004-07-07 23:50 ` [PATCH] FAT: update document Andries Brouwer
2004-07-08 17:26 ` OGAWA Hirofumi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d637mxig.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.