Justin R. Knierim wrote:
Nevermind, I just tried with the 6.2-pre3 LiveCD and I can't reproduce
the error either. Sorry for the noise, I can't figure it out.
The issue is probably that the old root password contained some
non-ASCII character, and someone recently changed the password to
Randy McMurchy wrote:
Justin R. Knierim wrote these words on 02/09/06 09:50 CST:
IMO he isn't blaming BLFS for problems with UTF-8.
Then you and I read plain English differently. IMO, the following
statement directly conflicts with what you say above:
But it is indeed better to say
Alexander E. Patrakov wrote:
Justin R. Knierim wrote:
Nevermind, I just tried with the 6.2-pre3 LiveCD and I can't
reproduce the error either. Sorry for the noise, I can't figure it out.
The issue is probably that the old root password contained some
non-ASCII character, and someone
Alexander E. Patrakov wrote these words on 02/08/06 22:52 CST:
But it is indeed better to say no to UTF-8 support now, because of
BLFS issues and because UTF-8 support is a property of the whole system,
not just its base. The blacklist approach (If a package is not listed
here, it means
Randy McMurchy wrote:
snip
IMO he isn't blaming BLFS for problems with UTF-8. Alexander has
publically stated that after adding UTF-8 to LFS, that maybe it really
isn't ready for the main book. Even asking to revert it or put it in an
experimental branch.
Justin R. Knierim wrote these words on 02/09/06 09:50 CST:
IMO he isn't blaming BLFS for problems with UTF-8.
Then you and I read plain English differently. IMO, the following
statement directly conflicts with what you say above:
But it is indeed better to say no to UTF-8 support now, because
Justin Knierim wrote:
There
are other problems, such as people not wanting the bloat, english
speakers not seeing the need, etc.
Just to clarify: As an English (only) speaker, I really don't want
UTF-8 on *my* system. As a BLFS developer, I certainly understand the
desire and need for
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
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
Jeremy Huntwork wrote:
I tried looking for the error using a recently built LFS LiveCD. I've
been using en_US.UTF-8 as a locale with it recently, and ssh both
incoming and outgoing has worked fine for me.
Logging in is fine. Once you are in, try su - root.
Justin
--
Justin R. Knierim wrote:
Jeremy Huntwork wrote:
I tried looking for the error using a recently built LFS LiveCD. I've
been using en_US.UTF-8 as a locale with it recently, and ssh both
incoming and outgoing has worked fine for me.
Logging in is fine. Once you are in, try su - root.
Worked
Jeremy Huntwork wrote:
Worked fine here... I will note that, seeing that I'm using a german
locale, my keys were a bit askew. The 'z' and the 'y' were reversed
and the '-' was where the '/' key is. Other than that, it worked fine.
Hmm, strange. I wasn't using the German profile when I
Justin R. Knierim wrote:
Hmm, strange. I wasn't using the German profile when I reported that
problem, it was the normal en_US.UTF-8. Anyways, I'll try it again
tonight and see what I can find.
Nevermind, I just tried with the 6.2-pre3 LiveCD and I can't reproduce
the error either.
Alexander E. Patrakov wrote:
some tme ago I imported from DIY linux the statement that none of the
locales are really required. As it stands now, this statement is wrong.
When checking whether the ctype macros accept non-ascii characters, Bash
configure script attempts to set the
Greg Schafer wrote:
Correct. However, the problem is with Readline and not Bash.
You are of course right. Thanks for the correction. I noticed this in
Chapter 5 as a difference between Glibc-based LFS and uClibc-based HLFS.
That's why I thought it's bash.
Now grep the Readline source for
15 matches
Mail list logo
