Bug 127763 - Installer breaks /etc/hosts convention
Installer breaks /etc/hosts convention
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: anaconda (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2004-07-13 11:18 EDT by Jason Dixon
Modified: 2007-11-30 17:06 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-07-13 11:31:14 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jason Dixon 2004-07-13 11:18:41 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Gecko/20040124 Galeon/1.3.14

Description of problem:
We performed a fresh install of AS 2.1 Update 4 and noticed some
changes with the /etc/hosts file that was created.  It produced the
following entry in /etc/hosts:   localhost.localdomain nodename

In the past, using the other Update CDs like Update 3 it would just
produce the following:   localhost.localdomain localhost
ip.address nodename.domain       nodename

We would like to find out why this change has occurred.  This is
breaking numerous applications.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.  Install RHAS 2.1 Update 4

Actual Results:  /etc/hosts file was "corrupted" as described above.

Expected Results:  Host->address mappings for network interfaces would
be appended on their own lines.

Additional info:
Comment 1 Jeremy Katz 2004-07-13 11:31:14 EDT
There were zero changes in anaconda for this in U4.  The diff in U4
includes adding an obsoletes in the package and commenting out a check
for the pid being over 100 in the anaconda script.

/etc/hosts has been being written out this way for years as doing it
in other ways breaks some servers starting up in cases where the
network isn't available (dhcp, laptops with pcmcia nics, etc)

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