Bug 63914 – hostname set during dhcp install

Bug 63914 - hostname set during dhcp install

Summary:	hostname set during dhcp install

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	anaconda (Show other bugs)
Sub Component:
Version:	7.3
Hardware:	i386 Linux

Priority	high Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Michael Fulbright
QA Contact:	Brock Organ
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	67218
	Show dependency tree / graph

Reported:	2002-04-21 16:33 EDT by Michael Redinger
Modified:	2007-03-26 23:52 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2002-08-15 08:28:33 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Michael Redinger 2002-04-21 16:33:02 EDT

Performing a kickstart installation of beta 4 using DHCP (network --bootproto dhcp), the resulting system does have a hostname set.

/etc/sysconfig/network:
HOSTNAME=.....

/etc/hosts:
127.0.0.1	NFQHN localhost.localdomain localhost


I think this is wrong ...

Comment 1 Jeremy Katz 2002-05-30 18:25:20 EDT

msf was looking at the network screen

Comment 2 Michael Fulbright 2002-08-14 17:45:21 EDT

What is NFQHN ?

Comment 3 Michael Redinger 2002-08-15 08:28:28 EDT

Oh, sorry. It's the hostname (not fully qualified, without the domain part).

Comment 4 Jeremy Katz 2002-08-19 14:44:49 EDT

This is the way we've always done things; otherwise sendmail and apache httpd
are unhappy trying to start

Comment 5 Michael Fulbright 2002-12-20 12:38:25 EST

Time tracking values updated

Note You need to log in before you can comment on or make changes to this bug.