Bug 16482 - hosts and resolv.conf miss entries after install
hosts and resolv.conf miss entries after install
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
7.0
noarch Linux
medium Severity high
: ---
: ---
Assigned To: Michael Fulbright
:
: 14501 14857 17492 17769 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-08-17 18:46 EDT by SAP LinuxLab
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-03-07 17:39:03 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description SAP LinuxLab 2000-08-17 18:46:09 EDT
a well-known bug in 6.1 was, that the installer would not write the
/etc/hosts and the /etc/resolv.conf with the entries supplied from the
"network" part of the install info.

The 7.0rc1 installer does even worse:
after the install, the hosts file contains only 1 line, e.g.

127.0.0.1               ls3034 localhost.localdomain localhost

and the resolv.conf contains only the "nameserver ..." -line.
Comment 1 Nalin Dahyabhai 2000-08-17 19:31:30 EDT
Reassigning to the installer.
Comment 2 Erik Troan 2000-08-22 11:53:01 EDT
We haven't figured out a solution that pleases more then 50% of the people
(including roaming
laptop users) yet :-(
Comment 3 Michael Fulbright 2000-09-14 15:01:07 EDT
*** Bug 17492 has been marked as a duplicate of this bug. ***
Comment 4 Michael Fulbright 2000-09-14 16:15:17 EDT
*** Bug 14857 has been marked as a duplicate of this bug. ***
Comment 5 Michael Fulbright 2000-09-14 16:40:44 EDT
*** Bug 14501 has been marked as a duplicate of this bug. ***
Comment 6 Michael Fulbright 2000-09-14 17:56:58 EDT
*** Bug 13486 has been marked as a duplicate of this bug. ***
Comment 7 Michael Fulbright 2000-10-06 17:50:45 EDT
*** Bug 17769 has been marked as a duplicate of this bug. ***
Comment 8 Jeremy Katz 2003-03-07 17:39:03 EST
This behavior isn't going to change at present since it seems to be correct the
most often of any solution.

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