In a perfect world, the functionality in the newer RFC that
I mentioned would communicate the client's locale to the server,
and they'd both behave in a way that took that into account
(including filename expansion, presumably).

AFAIK (from a very quick and brief look at the code), the current
Solaris command line ftp client does _not_ implement that
functionality - nor does its ftp server.

So on an "mput", I'd suppose that the client _might_ take the locale
into account, and on an "mget", the server would use whatever its
default locale was.  But that's just a guess.

(Although I don't actually see any mention in RFC2640 of using the
locale passed with the LANG command to adjust filename expansion,
but I haven't read the entire RFC, either.)

Solaris ftp and ftp handle multibyte (UTF-8) names correctly simply
because UTF-8 is what's used natively for multibyte names, and is also
what's specified for ftp transfers.  But they don't do all the rest of
what's required to make it a good experience.   So ftp transfers between
Solaris (and in general, probably between most Unix) systems should
work ok, but I wouldn't count on anything else working.  Even between
Solaris client and server, if it were me, I'd do some tests to see whether
mget and mput worked the way I wanted before depending on it.

There is at least one free ftpd that claims to implement
LANG, HOST, FEAT, and OPTS (last two RFC2389)...and claims
to build on Solaris.
http://www.pro-bono-publico.de/projects/ftpd.html

There may be others, but that's as far as I've looked, since I don't
need this functionality myself.

I haven't looked for a command line ftp client that implements the
various commands newer than RFC959.  I'm not that interested.
But it didn't take me very long to find a server (which I think
is really the first step).  So I expect there probably is one, somewhere.

I get the feeling that very few people really care about new functionality
in ftp.  As long as the old (RFC959) functionality works so that their
old stuff doesn't break, most seem to be ok with doing anything
newer on the web instead.

If you feel differently, why don't you do the research, see what
clients and servers work best for you, and maybe which are
reasonably compatible (esp. the server) in features and log file
format(s) with the wu-ftpd that's on Solaris now.  Maybe if you found
(or submitted a patch) something that was compatible enough,
had an acceptable license, and did what you wanted, you might
be able (esp. if you had a support contract, these days) to persuade
someone to take the time to look at whether it would be worth
replacing the existing ftp client and server with those.
-- 
This message posted from opensolaris.org
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Reply via email to