[wplug] dumb question of the day? how do I name a machine in rh9?

[Vanco, Don]

wplug-admin at wplug.org wrote:
> Thanks Don,
> 
> Turns out the question was even dumber than I thought at
> first. This is
> what I get for coming from the Mac part of the world -- I'm used to
> actually naming the *machine* itself which is what shows on the
> network. There is actually a similar but longer name that gets
> registered in the DHCP database of course. I am precisely in the
> process of getting the requested name registered with our facilities
> for the DHCP route. 

	Actually, if it's what it sounds like it's pretty standard fare -
"machine name" (i.e. hostname) -vs- FQDN (Fully Qualified Domain Name)
My machine is lappydappydoo but it's FQDN is lappydappydoo.agilysys.com -
some internal networks can get even more convoluted than that....

	In an interesting move I have been asked not to generate any machine
names with "crap" in them.  I deal with a lot of Windoze machines, and had a
bad habit calling them things like "vanco_crap_box"... apparently our NT
SysAdmins (ha! oxymoron there...) took offense.....  So I now use "carp".

Don

> On Thursday, January 8, 2004, at 03:03  PM, Vanco, Don wrote:
> 
>> wplug-admin at wplug.org wrote:
>>> Hi all,
>>> 
>>> Would that I could just show up at the install fest for all of
>>> this. <sigh> 
>>> 
>>> So, my dumb question. Now that I have the basic rh9 installed (and
>>> am tweaking with updates, etc), did I somehow miss a step to net
>>> the name
>>> of the machine as it would be recognized on, say the CMU network? I
>>> have been requested to give it a specific name (basically in CMU CS
>>> naming convention if that makes sense).
>>> 
>>> Thanks too to Beth Lynn for burning disks for me to enable to
>>> loading of this unit!!!
>> 
>> Method one: (if you get an address via DHCP)
>> 	Contact your network administrator and have them make it part of
>> 	your DHCP information (or follow method two)
>> 
>> Method Two:
>> 	redhat-config-network
>> 
>> 	There is a tab to assign hostname.
>> 
>> 	If/when either one or two is completed:  "service network restart"
>> 
>> 
>> 	If you do this in X, exit immediately and restart X to avoid
>> "interesting behavior". 
>> 
>> Don