Comment 5 for bug 178831

bluebox was the hostname when i installed feisty.
IWNETZ was the Workgroup when i used samba to connect with vmware.
System5 is the hostname now (/etc/hostname), but i don't remember when and how i changed it.
To reproduce it i startet gutsy and done this:

login
-----------------
  engl@SystemA:~$ cat /etc/hostname
  SystemA
  engl@SystemA:~$ cat /etc/hosts
  127.0.0.1 localhost
  127.0.1.1 SystemA

  # The following lines are desirable for IPv6 capable hosts
  ::1 ip6-localhost ip6-loopback
  fe00::0 ip6-localnet
  ff00::0 ip6-mcastprefix
  ff02::1 ip6-allnodes
  ff02::2 ip6-allrouters
  ff02::3 ip6-allhosts
---------------------------
System->Administration->Network->General->Hostname: SystemA=>SystemB
---------------------------
logout/login
---------------------------
  engl@SystemB:~$ cat /etc/hostname
  SystemB
  engl@SystemB:~$ cat /etc/hosts
  127.0.0.1 localhost
  127.0.1.1 SystemB
...
---------------------------------
I can't reproduce the change from SystemB to SystemB.IWNETZ, so edit the file /etc/hosts.
---------------------------------
  engl@SystemB:~$ cat /etc/hosts
  127.0.0.1 localhost
  127.0.1.1 SystemB.IWNETZ
...
---------------------------------
restart
----------------------
System->Administration->Network->General->Hostname: SystemB=>SystemC
-----------------------
log out/log in
-----------------------
  engl@SystemC:~$ cat /etc/hostname
  SystemC
  engl@SystemC:~$ cat /etc/hosts
  127.0.0.1 localhost
  127.0.1.1 SystemB.IWNETZ
...
-----------------------

I don't know, whether it was a bug under gutsy (or feisty?) that added .IWNETZ to the line in /etc/hosts, but there may be some computers having such a (defective?) /etc/hosts and these computers may have a problem when upgrading to hardy.
The situation
  $ cat /etc/hostname
  MyHostname
  $ cat /etc/hosts
  127.0.0.1 localhost
  127.0.1.1 MyHostname.MyWorkgroup
  ...
works under Gutsy, but not under Hardy.