Red Hat Bugzilla – Bug 76819
Unable to enter hostname and dns info
Last modified: 2007-04-18 12:47:58 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020830
Description of problem:
WHen anaconda gets to the network config screen it will not allow hostname or
dns info to be entered.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Install RH 8.0 CD #1 into drive
2.Start Installing RHL 8.0
3.When it gets to network config, after enetering ip for eth0 you can't
enter hostname, gateway or dns info
Actual Results: Unable to enter hostname, gateway or dns info.
Expected Results: Able to enter system hostname, gateway and dns info.
I was configuring eth0 with a static ip, mistakenly entered ip in hostname
field, after that it would not allow anything to be entered into the hostname,
gateway or dns fields. This machine has does have 4 nic cards. Dell P330, with
an additional 3C905, EEPRO100 and realtek card. If I restart and no make no
incorrect entries it is ok. Other nuisances, not installing bootloader, /boot on
/dev/sda9 and / on sda10, existing sway on /dev/sda6 being used.
I could not reproduce this error report.
Was this error in the text mode network configuration screen used when
specifying your install source, or later once the stage 2 installation is
running and you are given an option to adjust your network settings?
This was induced by going past the original network screen and then going back.
I have a suspiscion this is related to the neat bugs. Take a look at bug 75266,
simillar types of issues. It sure seems related to me :-) , but I'll let the
experts make the final call on that.
Even with 8.093 it is very easy to get the installer in this funky condition.
This time I was not able to enter root password.
This should probably be rolled into bug# 84483 or vice versa, basically same
problem but it presnets itself differently during installs.
This should be better in our current code.
Mass-closing lots of old bugs which are in MODIFIED (and thus presumed to be
fixed). If any of these are still a problem, please reopen or file a new bug
against the release which they're occurring in so they can be properly tracked.