Please pardon the resend of this message, but this has been a much asked about issue recently. So, I am again addressing this in order to add a few key points. Given that the Speakup Modified is still not ready, telnet installation of stock Fedora Core 4 is a viable option--but there are issues people should know about. So, in an effort to get the essential facts into a single message, I'm resending this note with a few key additions. Of course, here on the Speakup list, that means two messages because of the message size limit. How To Do A Telnet INstall Of FC4 -- Part 1 Of 2 1.) Follow the guidance in the Speakup Modified Installation HOWTO for FC3 up to the point where it talks about what to type at the Boot> prompt. The guidance provided to that point is still accurate and relevant. 2.) At the Boot> prompt issue a command like the following. You will not have speech feedback during this process, so backspace the entire line off if you think you have made a mistake, and retype it. It's a lot of typing, but you need to get all these details in. This command must be issued on one line, even though it has probably been wrapped into at least two lines in this message. text telnet ip=[ip.address] netmask=[netmask] gateway=[gateway.address] ksdevice=[ethernet.device] Example: text telnet ip=192.168.33.123 netmask=255.255.255.0 gateway=192.168.33.254 ksdevice=/dev/eth1 All on one line, of course. In the above ksdevice refers to your ethernet device designation. You can leave this part out if the machine you're installing on has only one ethernet device (namely /dev/eth0). But, if you're installing on a computer with multiple devices, e.g. a portable computer with a wired ethernet port and builtin wireless ethernet, you will be prompted inaccessibly on screen for the ethernet device the Fedora installer should use if you don't just tell the installer up front which one to use with the ksdevice designation. So, be sure to include it. If in doubt, use it and try ksdevice=/dev/eth0. 3.) Then, ping the ip address you provided with your command. When you get a response, telnet to it. TIP: If you are on Linux, use alarm ping, e.g.: ping -a 192.168.33.123 When your ping starts singing, it's time to telnet to the installation. telnet 192.168.33.123 Be aware that it takes some time for the telnet server to get loaded and become available. The installation must first load its various drivers and this will take some time--perhaps a few minutes. [Continued in a subsequent message]
