Package: hostname Version: 2.91 Severity: normal Ok. This is the anti-bug to #239888. Sometime after Sarge was released /bin/hostname started telling me all my hostnames, such as "pride.fud.no", is invalid (due to the periods).
In #239888 I see a example of a person who believe this is illegal (indeed, even "disgusting", "insane", and more). No reason for this view was supplied, though, even after I explicitly asked for one. I have used FQDN hostnames since I started using Linux 10 years ago, and have yet to see any ill effects from it. It has been allowed in Debian, SuSE, Red Hat, and probably the rest of the various distributions as well. I just tested Solaris 10, which has no problems using FQDN hostnames either. So this new behaviour appears to be Debian-specific, and I have not had any success in finding any rationale for the change either. Please revert the change, or at the very least document why it is now necessary for Debian to behave differently than everyone else. Kind regards Tore Anderson -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.14-2-k7 Locale: LANG=it_IT.ISO-8859-1, LC_CTYPE=it_IT.ISO-8859-1 (charmap=ISO-8859-1) Versions of packages hostname depends on: ii libc6 2.3.5-8.1 GNU C Library: Shared libraries an hostname recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
