When in F7T2, the terminal prompt lists my computer as localhost, even though I gave it a name during install. [root@localhost ~]# When in F7T1, it lists my computer as F7T1, the name I gave it when installing from DVD. [root@f7t1] ~]# The /etc/hosts files have the same form: [root@localhost ~]# diff /etc/hosts /mnt/f7t1/etc/hosts 3c3 < <a href="http://127.0.0.1" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> 127.0.0.1</a> <a href="http://f7t2.thetoolshed.us" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> f7t2.thetoolshed.us</a> f7t2 localhost.localdomain localhost --- > <a href="http://127.0.0.1" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">127.0.0.1</a> <a href="http://f7t1.thetoolshed.us" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> f7t1.thetoolshed.us</a> f7t1 localhost.localdomain localhost This naming persists, even though I set hostname with the hostname command. The next time I boot to f7t2, the hostname is back to "localhost" [root@localhost ~]# hostname localhost [root@localhost ~]# hostname <a href="http://f7t2.thetoolshed.us" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">f7t2.thetoolshed.us</a> [root@localhost ~]# hostname <a href="http://f7t2.thetoolshed.us" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> f7t2.thetoolshed.us</a> In f7t1: [root@f7t1 ~]# hostname <a href="http://f7t1.thetoolshed.us" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">f7t1.thetoolshed.us</a> Here are the /etc/sysconfig/network file contents: [root@localhost ~]# cat /etc/sysconfig/network NETWORKING=yes yesHOSTNAME=<a href="http://f7t2.thetoolshed.us">f7t2.thetoolshed.us</a> [root@localhost ~]# cat /mnt/f7t1/etc/sysconfig/network HOSTNAME=<a href="http://f7t1.thetoolshed.us">f7t1.thetoolshed.us </a> NETWORKING=yes yesHOSTNAME=<a href="http://f7t1.thetoolshed.us">f7t1.thetoolshed.us</a> There was a bug in F7t1 anaconda (bugzilla #227250) that didn't honor the host name set by the user; is that still the problem? Or, is there something I'm forgetting to do? I added this comment to the bug report. In this case, removing the yes from yesHOSTNAME and restarting the network does not solve the naming problem. [root@localhost ~]# service network restart Shutting down interface eth0: [ OK ] Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface eth0: Determining IP information for eth0... done. [ OK ] [root@localhost ~]# Gerry