From: Pavel Fedin <sonic_amiga@rambler.ru>
To: Andrew Morton <akpm@osdl.org>
Cc: Roman Zippel <zippel@linux-m68k.org>, linux-fsdevel@vger.kernel.org
Subject: Re: Fw: [PATCH] Full NLS support for HFS (classic) filesystem
Date: Tue, 30 Aug 2005 10:13:23 +0400 [thread overview]
Message-ID: <4313F903.6010101@rambler.ru> (raw)
In-Reply-To: <20050829134533.541465d2.akpm@osdl.org>
Andrew Morton wrote:
> So I have this very old patch sitting in my todo folder. Has it moved forward at all?
Roman Zippel didn't agree with such an implementation and created
another version which is the only proper one as he says (despite it's
less functional). Well, i am waiting for it to appear in "stable" kernel
in order to re-add CP10007 NLS and re-test it.
You can cut out cp10007 NLS from this patch and apply it to the
kernel, it is absent in Andrew's version because he is not russian.
I am copying this message to Roman for reference.
P.S. I still would like to take the following changes into consideration:
1. IMHO all the filesystems in the kernel should ignore unknown
arguments rather than raise an error and refuse to mount. This would
make autofs much more usable. For example line like:
/dev/cdrom /mnt/cdrom hfsplus,hfs
user,noauto,iocharset=koi8-r,codepage=10007
would work in this case. Currently it would fail because hfsplus knows
nothing about "codepage".
There can be more examples where ignoring unknown arguments would be
useful, this is just the most common one for me.
A side-effect would be fixup of smbfs which currently doesn't
recognise "user,noauto". I posted a patch introducing these dummy
arguments a long time ago but it was rejected because it was considered
to be just a code pollution. Probably a policy of ignoring all unknown
arguments would do?
2. There are two arguments doing the same job. Some filesystems
understand only "nls" and some - only "iocharset". I think this should
be made uniform.
Kind regards.
parent reply other threads:[~2005-08-30 6:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20050829134533.541465d2.akpm@osdl.org>]
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=4313F903.6010101@rambler.ru \
--to=sonic_amiga@rambler.ru \
--cc=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=zippel@linux-m68k.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.