From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
Jeff Layton <jlayton@redhat.com>,
steved@redhat.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/4] nfs-utils: introduce new statd implementation (1st part)
Date: Thu, 10 Sep 2009 11:03:19 -0400 [thread overview]
Message-ID: <20090910150319.GA10704@fieldses.org> (raw)
In-Reply-To: <D2B488FA-2630-4355-8E3B-FE1243E4C3AE@oracle.com>
On Wed, Sep 09, 2009 at 06:18:11PM -0400, Chuck Lever wrote:
> IDNs are UTF16. /var therefore has to support UTF16 filenames; either
> byte in a double-byte character can be '/' or '\0'. That means the
> underlying fs implementation has to support UTF16 (FAT32 anyone?), and
> the system's locale has to be configured correctly. If we decide not to
> depend on the file system to support UTF16 filenames, then statd has to
> be intelligent enough to figure out how to deal with converting UTF16
> hostnames before storing them as filenames. Then, we have to teach
> matchhostname() and friends how to deal with double-byte character
> strings...
Googling around.... Is this accurate?:
http://en.wikipedia.org/wiki/Internationalized_domain_name
That makes it sound like domain names are staying ascii, and they're
just adding something on top to allow encoding unicode using ascii,
which may optionally be used by applications.
--b.
next prev parent reply other threads:[~2009-09-10 15:03 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 14:45 [PATCH 0/4] new statd [take 2] Chuck Lever
[not found] ` <20090805143550.12866.8377.stgit-RytpoXr2tKZ9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2009-08-05 14:45 ` [PATCH 1/4] nfs-utils: introduce new statd implementation (1st part) Chuck Lever
[not found] ` <20090805144540.12866.22084.stgit-RytpoXr2tKZ9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2009-08-05 17:48 ` J. Bruce Fields
2009-08-05 18:05 ` Chuck Lever
2009-08-05 18:15 ` J. Bruce Fields
2009-08-05 18:26 ` Chuck Lever
2009-08-05 21:22 ` Trond Myklebust
[not found] ` <1249507356.5428.11.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-08-05 22:24 ` Chuck Lever
2009-08-05 23:30 ` Trond Myklebust
2009-09-09 18:29 ` Jeff Layton
[not found] ` <20090909142945.755da393-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2009-09-09 18:39 ` Trond Myklebust
2009-09-09 19:13 ` Jeff Layton
[not found] ` <20090909151354.504ccdf6-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2009-09-09 19:19 ` Chuck Lever
2009-09-09 19:17 ` Chuck Lever
2009-09-09 19:42 ` Trond Myklebust
2009-09-09 22:18 ` Chuck Lever
2009-09-09 23:15 ` Steve Dickson
2009-09-10 15:01 ` Chuck Lever
2009-09-10 8:44 ` NeilBrown
2009-09-10 14:09 ` Chuck Lever
2009-09-14 7:08 ` Neil Brown
[not found] ` <19117.60405.793389.323010-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2009-09-14 15:48 ` Steve Dickson
2009-09-15 2:45 ` Chuck Lever
2009-09-14 13:54 ` Trond Myklebust
[not found] ` <1252936467.6866.54.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-09-14 15:55 ` Steve Dickson
2009-09-15 1:29 ` Chuck Lever
[not found] ` <9eae93545189a6be6eebe0460b860fc7.squirrel-eq65iwfR9nKIECXXMXunQA@public.gmane.org>
2009-09-10 15:05 ` bpm
2009-09-10 15:03 ` J. Bruce Fields [this message]
2009-09-10 16:14 ` Chuck Lever
2009-09-10 16:23 ` J. Bruce Fields
2009-09-10 16:43 ` Trond Myklebust
2009-09-10 20:39 ` Chuck Lever
2009-09-10 20:49 ` J. Bruce Fields
2009-09-10 21:26 ` Chuck Lever
2009-08-05 14:45 ` [PATCH 2/4] nfs-utils: introduce new statd implementation (2nd part) Chuck Lever
2009-08-05 14:46 ` [PATCH 3/4] nfs-utils: introduce new statd implementation (3rd part) Chuck Lever
2009-08-05 14:46 ` [PATCH 4/4] nfs-utils: introduce new statd implementation (4th part) Chuck Lever
2009-08-05 17:15 ` [PATCH 0/4] new statd [take 2] Jeff Layton
[not found] ` <20090805131554.67eb15bc-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2009-08-05 18:06 ` Chuck Lever
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=20090910150319.GA10704@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.com \
--cc=trond.myklebust@fys.uio.no \
/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.