On 2009-12-31 16:35:58 +0100, Iustin Pop wrote: > This is a personal opinion, but having the canonical name rely on > “hostname --fqdn” is not a favorite of mine: hostname needs the resolver > to be working and functioning (e.g. it talks to your nameservers if > /etc/hosts doesn't contain your hostname/ip already).
Well, the practice, the FQDN is often available via /etc/hosts. > IMHVO, this is a brittle setup and the FQDN should be available directly > on the host, without external dependencies. Which is why I personally > think the machine name (the one that the kernel knows) should hold the > canonical name. Either that, or having the FQDN in /etc/hosts. I don't see any problem with that, excepts that iceweasel doesn't cope very well with this: lrwxrwxrwx 1 vinc17 vinc17 15 2009-12-30 05:35:38 lock -> 127.0.1.1:+5537 I wonder why it doesn't use the FQDN. The IP addresse 127.0.1.1 is incorrect when the directory is shared with other hosts. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <http://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
