Bug 19632 - reconfig doesn't configure network
Summary: reconfig doesn't configure network
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.0
Hardware: i386
OS: Linux
medium
low
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-10-23 20:36 UTC by Need Real Name
Modified: 2007-04-18 16:29 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2000-10-30 21:42:38 UTC
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2000-10-23 20:36:33 UTC
`anaconda --reconfig` does not prompt for network
information when started from the initscripts.

i can only get it to work by pre-loading the module
for my nic (eepro100).

maybe add a `/sbin/modprobe eth0` to /etc/init.d/reconfig?
that works fine for me, and would fall through cleanly to a 
no-LAN case if there is no `alias eth0` line in /etc/modules.conf

Comment 1 Michael Fulbright 2000-10-30 21:03:43 UTC
I have verified this appears to be an issue.

Comment 2 Need Real Name 2000-10-30 21:42:36 UTC
although my workaround (loading the eth0 module) allows anaconda --reconfig
to succeed, it sets the hostname improperly.
(it looks like it may be trying to do a reverse nslookup, but of course the
network hasn't been brought up yet)
i.e., in /etc/sysconfig/network, it sets the hostname to localhost.localdomain.
/etc/hosts does not contain the proper hostname either.

the workaround i'm using here is parsing the user-defined hostname out of
/tmp/reconfig.log, and modifying /etc/hosts and /etc/sysconfig/network
accordingly.
-dann

Comment 3 Michael Fulbright 2001-02-08 20:53:38 UTC
Network configuration should be done using the other system configuration tools
in a post-install environment.


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