Red Hat Bugzilla – Bug 173072
Loader stalls when doing telnet installation
Last modified: 2007-11-30 17:07:21 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.12) Gecko/20050919 Firefox/1.0.7 (ax)
Description of problem:
When trying to perform a text mode telnet installation on RHEL4U2 the telnet connection is immediately dropped upon the telnet connection attempt
If you use 'linux text telnet dhcp' as the boot line the system boots and displayed the message 'waiting for telnet connection' but as soon as you connect the telnet is dropped and installation proceeds as if telnet was not used.
If you use 'linux text telnet ip=x.x.x.x netmask=x.x.x.x' the system boots and appears to freeze on the 'running /sbin/loader' line until a telnet connection is established at wich point the connection is dropped and install proceeds as above.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot from a RHEL4U2 CD
2. Use 'linux text telnet ip=x.x.x.x netmask=x.x.x.x.x' or 'linux text telnet dhcp' as the boot line
3. Ping the host until it replies (use Alt+F3 to determine IP address if using dhcp).
4. Once it replies or the 'waiting for telnet connection' box appears attempt to connect using telnet.
Actual Results: Boot up proceeds as normal and either stops on 'waiting for telnet connection' or 'running /sbin/loader' prompt.
Expected Results: Installer should allow (i.e. not drop) the telnet connection and display the installer the the remote workstation telnet client.
Telnet seems to work fine using these steps on Fedora Core 4.
Have tried using telnet from Windows (XP & 2000) as well as Gnome Terminal on Fedora Core 4.
The Alt+F3 console shows the following messages during bootup which may be
* going to BeTelnet for my.ip.address
* cannot open /dev/ttyp0
*** Bug 173074 has been marked as a duplicate of this bug. ***
This problem will be resolved in a future major release of Red Hat Enterprise
Linux. Red Hat does not currently plan to provide a resolution for this in a Red
Hat Enterprise Linux update for currently deployed systems.
With the goal of minimizing risk of change for deployed systems, and in response
to customer and partner requirements, Red Hat takes a conservative approach when
evaluating changes for inclusion in maintenance updates for currently deployed
products. The primary objectives of update releases are to enable new hardware
platform support and to resolve critical defects.
I don't see what the risk of change is. It is a feature that is already
included in the system but is current broken, there must be a bug fix of some
kind for it as it works with Fedora.
If you don't plan to fix this please stop advertising it as a feature. I only
heard about this when logging another bug and was advised by (I believe) a
redhat developer/support person to use this feature.
End of rant.