Re: UTF-8 practically vs. theoretically in the VFS API (was: Re: JFS default behavior)
From: Dave Kleikamp (shaggy_at_austin.ibm.com)
Date: 02/17/04
- Previous message: Harald Welte: "Re: POSSIBLE BUG: netfilter/ip_conntrack_core"
- In reply to: Marc Lehmann: "Re: UTF-8 practically vs. theoretically in the VFS API (was: Re: JFS default behavior)"
- Next in thread: Jamie Lokier: "Re: UTF-8 practically vs. theoretically in the VFS API (was: Re: JFS default behavior)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: Marc Lehmann <pcg@schmorp.de> Date: Tue, 17 Feb 2004 08:12:26 -0600
On Mon, 2004-02-16 at 14:58, Marc Lehmann wrote:
> True. Thanks a lot for explaining your arguments in this detail. In
> fact, I can accept most if not all of your arguments, but I sitll think
> it would be nice to have this extra functionality.
>
> Arguments like "it's a pain to implement" (which I don't think it is, but
> you are clearly better in judging that!), weigh even more to me.
>
> So even if I think it's a good idea, it might never be implemneted for
> purely practical reasons.
Use jfs with the mount option iocharset=utf8 and you'll get exactly what
you are asking for.
-- David Kleikamp IBM Linux Technology Center - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Harald Welte: "Re: POSSIBLE BUG: netfilter/ip_conntrack_core"
- In reply to: Marc Lehmann: "Re: UTF-8 practically vs. theoretically in the VFS API (was: Re: JFS default behavior)"
- Next in thread: Jamie Lokier: "Re: UTF-8 practically vs. theoretically in the VFS API (was: Re: JFS default behavior)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]