For URLs such "telnet://", "rlogin://" etc, Lynx uses TELNET_PATH, RLOGIN_PATH and so on configuration options. By default, when such options is not set, Lynx uses compiled-in ones. In the earlier releases, Lynx caught just the first suitable telnet at the build machine (usually /usr/kerberos/bin/telnet). Now, when building performs in the clear "mock" environment, there is no any telnet, hence Lynx knows nothing about it and friends... In other words, after upgrading from FC5 to F7, the "telnet://" URLs no more work under Lynx, because of the reason described above. To solve this issue, please, add "TELNET_PATH:telnet" (and may be similar for another protocols) into default /etc/lynx.cfg config file.
Hi, are you sure you have telnet on your machine? When I try to use URL telnet://.. it works even thought I don't have TELNET_PATH set in lynx.cfg. Jirka
I had modified rpm on my machine installed and as I found out you're right, it doesn't work without TELNET_PATH, but I'm not sure if I should modify the cfg file that way, I think this should be up to user to set this path ...
> up to user to set this path Nope. Actually, Lynx undestands the PATH environment variable. Hence it catch the first suitable telnet according to the PATH (either /usr/kerberos/bin/telnet, or /usr/bin/telnet, or even /usr/local/bin/telnet). Thus, for default installation, we may specify just the short "telnet" without the full path. The same is true for another similar externals, like "rlogin" etc. I think all the list (around commented TELNET_PATH in the lynx.cfg) should be inspected for missing default values, and then lynx.cfg patched to set the default values for them (where applicable) ...
lynx-2.8.6-10.fc8 has been submitted as an update for Fedora 8
lynx-2.8.6-5.fc7 has been submitted as an update for Fedora 7
lynx-2.8.6-5.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.
lynx-2.8.6-10.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.