The K Desktop Environment
Spaghetti Code Computing

This documentation describes the features of version 0.63
 
 
    1. Introduction
    2. Using KTelnet
    3. Keybindings
    4. Working with rlogin
    5. Using xhost
    6. Setting up ports
    7. Terminals
    8. Creating KDElnk files
    9. Commandline arguments
    10. Panelize KTelnet
    11. Release Notes
    12. Bugreports
    13. Updates



  1. Introduction

    2. KTelnet is a frontend to the programs telnet, rlogin and secure shell. But it is even more. It is an easy way for beginners to learn how to work in a network efficiently. KTelnet is part of the KDE  (the  K Desktop Environment).
    KTelnet also provides you with the possibility to start an ordinary terminal (xterm, kvt, rxvt...) if you set the host to "-" and the account to "-".
    All sessions can be configured separately without learning the terminals command line parameters.

  2. Using KTelnet

    3. Before connecting to a remote host you have to add a new session. Therefore select "New Session" in the File Popupmenu or the Toolbar. Edit all fields. The "Further options" are optional. Then press "Accept" to accept the new session or "Cancel" to reject editing.

    Note:

    New sessions must be saved by choosing "Save sessions" in the file menu. You can also call KTelnet to do that automatically on exiting in the Options tabdialog.

  3. Keybindings

    4. To prevent you from damaging your mousebuttons by clicking the hole day, KTelnet also provides you with some needful keyboard accelerators. These are (+ the accelerators within the menus):

  4. Working with rlogin

    5. If you are working with rlogin, you can connect to remote machines without typing your passwort at each login. Just write a file in your home directory of the remote machine with the name ".rhosts". In this file you have to type the machine's name and account name from where you want to log in. Example: if user Nick on machine Linux1 wants to log in account nick on Linux2 he has to write a file .rhosts on machine Linux2 with the following contents: 
    Linux1 Nick
    Now, he does not need to type any password any more.

  5. XHost

    6. XWindows is a network transparent windows system, that means that you can start an application on server and display the resulting window on client. If you log onto server, a environment varible, called DISPLAY will normally be set to server:0.0. The result is,that all X Apps you start on server tell you something like "Can't connect to X Server". The programs want to open on the wrong screen. If you set the variable DISPLAY by (bash) 
    export DISPLAY=client:0.0
    then the applications try to open their windows on client. Now, client is refusing connection until you tell client that server is allowed to open windows. This is done be xhost. KTelnet can be configured that way, that it calls xhost for your host before opening the terminal. What you have to do, is to set your DISPLAY variable on server. This can not be done by KTelnet. Unfortunately.

    All this is not needed when you use ssh (Secure Shell) because ssh has its own X channel so server will automatically open programs on client and client does not refuse it.

  6. Setting up ports

    7. The connection programs try to call the host over a certain port. You can set up the port number within ktelnet. If you are not shure about what to do, leave the port number empty or set it to zero. Then ktelnet always connects to the default port. This is 23 for telnet and 22 for secure shell (as far as I know). Sometimes the port numbers are changed. E.g. when using a slirp connection to the internet, you can redirect ports of your providers workstation to let your computer at home be a real internet server. How to do that is explained on my slirp homepage (in German).

  7. Terminals

    8. If you want to use another terminal which is not provided by ktelnet, you can add the terminal in the resource file and also add the terminal options for fontsize and colors there. I think you'll find it. See the global ktelnetrc and the section [terminal] inside. Only change anything if you know what you are doing or contact me. Of course, only these terminals can be used, which are installed on your local host (You probably won't find a hpterm on a DEC workstation).

  8. Creating KDElnk files

    9. KTelnet can create KDElnk files from your sessions. Just select the corresponding entry in the File menu and the currently displayed session will be saved into a kdelnk file. Of course, you can choose the destination for saving.

  9. Commandline arguments

    10. KTelnet now has some commandline arguments:
    1. --help: display the possible commandline arguments
    2. --panel: start KTelnet directly on the panel
    3. --session: start only a certain session. Usage: ktelnet --session "my session". KTelnet will return immediately after starting the session.

  10. Panelize KTelnet

    11. If you start KTelnet as ordinary window, you can choose "On panel" from the options menu to put KTelnet onto the panel. Once KTelnet is on the panel, you can start remote sessions by clicking the left mousebutton. Right mousebutton redisplays the main Window of KTelnet. To stop KTelnet from running, you always have to redisplay the main Window. Another possibility to panelize KTelnet is to simply click the "iconify" window button.

  11. Release Notes

  12. Bug reports

    13. If you find any bugs (I hope you will not) please send an E-mail to me, that is martin.haefner@topmail.de.

  13. Updates

    14. For new versions of KTelnet please contact the KTelnet homepage or see the applications list of K Desktop Environment

Next Previous Table of Contents

Written by Martin Häfner: martin.haefner@topmail.de