LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
agalakhov@ifmlrs.uran.ru, Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: [PATCH] Sanitize filesystem NLS handling
Date: Thu, 22 Mar 2007 18:22:11 +0500 [thread overview]
Message-ID: <46028303.7070104@ums.usu.ru> (raw)
In-Reply-To: <Pine.LNX.4.64.0703221350400.14458@scrub.home>
Roman Zippel wrote:
> I agree that these parameters should be changable not just at compile time
> and the iocharset should be a global default, but the on disk encoding is
> often filesystem specific, so I'd rather keep this option per filesystem.
You are right, the on-disk encoding is filesystem specific. E.g., it is
always UCS-2 for CIFS, NTFS and VFAT (and my patch doesn't change this).
It is exposed as a mount parameter and kernel configuration option only for
fat and smbfs (the two filesystems that my patch touches for this matter),
and both of these filesystems come from DOS days, where there was one
codepage for a given country. So, for me, it made sense to glue these two
parameters, because they both should be set to this codepage. The contrary
would (AFAIK) only make sense if one gets floppies from France, but
communicates with Polish SMB servers. It is a very rare situation, isn't it?
Or do you know any other example where it would clearly make sense to have
different defaults for fat and smbfs?
--
Alexander E. Patrakov
next prev parent reply other threads:[~2007-03-22 13:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-18 16:55 Alexander E. Patrakov
2007-03-18 22:01 ` OGAWA Hirofumi
2007-03-19 2:58 ` Alexander E. Patrakov
2007-03-19 3:46 ` OGAWA Hirofumi
2007-03-19 4:38 ` Alexander E. Patrakov
2007-03-19 5:38 ` OGAWA Hirofumi
2007-03-19 5:49 ` Alexander E. Patrakov
2007-03-19 14:25 ` OGAWA Hirofumi
2007-03-19 15:04 ` Alexander E. Patrakov
2007-03-19 17:26 ` OGAWA Hirofumi
2007-03-20 6:25 ` Alexander E. Patrakov
2007-03-21 16:50 ` OGAWA Hirofumi
2007-03-19 15:10 ` Alexander E. Patrakov
2007-03-19 17:36 ` OGAWA Hirofumi
2007-03-19 6:38 ` yes --help (was: [PATCH] Sanitize filesystem NLS handling) Bernd Eckenfels
2007-03-19 8:14 ` Alexander E. Patrakov
2007-03-22 12:59 ` [PATCH] Sanitize filesystem NLS handling Roman Zippel
2007-03-22 13:22 ` Alexander E. Patrakov [this message]
2007-03-22 13:49 ` Roman Zippel
2007-03-22 13:59 ` Alexander E. Patrakov
2007-03-22 15:45 ` Roman Zippel
2007-03-22 14:58 ` Alexander E. Patrakov
2007-03-22 16:07 ` Alexander E. Patrakov
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=46028303.7070104@ums.usu.ru \
--to=patrakov@ums.usu.ru \
--cc=agalakhov@ifmlrs.uran.ru \
--cc=akpm@osdl.org \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.org \
--subject='Re: [PATCH] Sanitize filesystem NLS handling' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).