Re: @%$#$ can't start on RH 7.1

Andy> Seems like you should turn it round the other way - how many Andy> people would be affected by the (so called) wrong behaviour? A few people, mostly in Japan, today. Far more, probably mostly in Japan :-), in the near future. Andy> Not many I imagine. Whereas the status quo has annoyed many. Yeah, it annoyed me, too. So I fixed my system. I think we should encourage others to do that where possible, rather than defaulting to not handling IPv6 at all. I think there probably are problems, like autodialing on attempts to use the network, that will be hard to configure around. But the CNAME hang on startup is not one; you simply need to not configure your nameservers until you have a working net connection. Every DHCP client does that already, and it should be reasonably easy to configure PPP that way too. Glynn> Note that these don't require any explicit support from the Glynn> application; XOpenDisplay(NULL) and XOpenDisplay(<arbitrary Glynn> string>) will do the right thing automatically. I can't wait until X11 gets getaddrinfo'ized then. Should be a spectacular flamefest. :-) Glynn> Maybe the canonicalisation code should go, and the value of Glynn> $DISPLAY just used as-is. Anything else is bound to get it Glynn> wrong in some cases. Seems likely. Do you have any examples? I wonder why they did it in the first place, though. However, we also do canonicalization in sysdep.c (init_system_name). Why that doesn't bite anyone, I don't know. I'm going to turn IPv6 off there, too, if --with-ipv6-lookup=no. Removing canonicalization entirely is something that isn't going to happen in 21.4.4, and probably won't happen soon thereafter, either. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."