Daniel Iliev <daniel.iliev@...> posted
20080630101630.787b95ae@..., excerpted below, on Mon, 30 Jun
2008 10:16:30 +0300:
> My glibc is (intentionally) not IDN-enabled, hence my problem with
> traceroute. Commenting out that line leads to compiling a working
> traceroute for my system.
Makes sense.
> Sorry, Duncan, but it seems your problem is not related and this info is
> not much help for you. :(
I'm not too worried about it, at least not yet. There's a good chance my
problem was a one-time thing, a combination of a testing version dhcpcd,
testing baselayout 2, perhaps the new glibc 2.8, and throw in a couple
recent lockups due to X issues after an upgrade that needed a different
config. Put them together, particularly with the lockups and resulting
unclean reboots, and there's at least a half-dozen different
possibilities. As mentioned, I already knew it wasn't directly related.
I simply threw it in as an odd occurrence, in the hope that it might
"click" with something else, giving you the solution. Evidently, it
really /was/ unrelated, but you read something about IDN and /that/
"clicked" for you. FWIW, I'd have never considered IDN either, but that
may well be because I'm pretty much en_US-only. So I'm glad you found
that IDN stuff and it /did/ click for you, because that would have
otherwise seemed just as unrelated to me as the resolv.conf overwrite did.
So yes, definitely thanks for posting that resolution. I'd have had not
the foggiest idea of looking /there/! Now I do, next time it comes up
for me or someone on a group I'm on. =8^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
gentoo-amd64@g.o mailing list
|
