Chris Staub wrote:
Joel Miller wrote:
Jeremy Huntwork wrote:
<snip>
And to further clarify, an LFS machine as it currently is does *not*
automatically use UTF-8. The changes to the LFS book are so that the
LFS system *can* use UTF-8 properly if a user requires it. IMO, this is
<snip>
I'd like some clarification on one point then. IIRC, I read in a post
by Alexander that the changes to the book made it so that ssh would no
longer connect properly to non UTF-8 systems. In order to do that you
had to run ssh through screen. This would be a *massive* inconvenience
issue for me. Is this the case just by following the new book
instructions, or is this only the case if you set your locale to a
UTF-8 locale?
Also, I recall him saying that the issue with ssh is not a bug - it has
something to do with the fact that ssh transfers "bytes" - not
"characters" (or something like that...) and is part of the basic nature
of the workings of ssh.
And, like all the other UTF-8 issues in the current book, it does not
apply if you use a non-UTF-8 locale. You shouldn't see any difference
whatsoever (aside from maybe a small - negligable? - size difference in
disk space and memory) from the not-UTF-8 book if you use a non-UTF-8
locale.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
