Terminal emulator

Bin mir nicht ganz sicher was du suchst. Als Terminal Emulatoren für 
Linux (X) fallen mir direkt xterm und rxvt ein, gibt aber sicherlich 
noch einige andere.

also für Linux gibts laut meinem Paketmanager:

- Minicom:
friendly menu driven serial communication program
Minicom is a clone of the MS-DOS "Telix" communication program. It 
emulates
ANSI and VT102 terminals, has a dialing directory and auto zmodem 
download.

- cutecom:
Graphical serial terminal, like minicom
Cutecom is a graphical serial terminal, like minicom.
It is aimed mainly at hardware developers or other people who need a
terminal to talk to their devices. It features lineoriented interface
instead of character-oriented, xmodem, ymodem, zmodem support
(requires the lrzsz package) and hexadecimal input and output among
other things.
It is written using the Qt library by Trolltech (www.trolltech.com).

-seyon:
X11-Kommunikationsprogramm mit vielen Features
Seyon ist ein komplettes Modemkommunikationsprogramm für
das X Window System. Einige Features sind:
 - Wählverzeichnis
 - Terminalemulation (DEC VT02, Tektronix 4014 und ANSI)
 - integrierte Skriptsprache
 - Zmodem

- wterm:
lightweight terminal emulator for X
wterm is a color VT102 terminal emulator for the X Window System.  While
lightweight, it provides an elegant interface including NeXTSTEP style 
scroll
bars and an application menu that integrates well with the Window Maker
window manager and GNUstep based applications.  wterm works well with 
any
window manager or desktop environment.

Features of wterm include background images, transparency, and reverse
transparency.  An extensive set or runtime options are available 
resulting in a very customizable terminal emulator.

und noch ein paar mehr.
seyon hab ich schon mal ausprobiert, ist halt ein altertümlicher 
"DOS-Bildschirm".

Unter Linux verwendest du entweder minicom (was ja auch hier schon 
genannt wurde) oder direkt screen:

   $ screen /dev/ttyS0 115200

Siehe auch folgender Eintrag in der Dokumentation:

   * If a tty (character special device) name (e.g. `/dev/ttya') is
     specified as the first parameter, then the window is directly
     connected to this device.  This window type is similar to `screen
     cu -l /dev/ttya'.  Read and write access is required on the device
     node, an exclusive open is attempted on the node to mark the
     connection line as busy.  An optional parameter is allowed
     consisting of a comma separated list of flags in the notation used
     by `stty(1)':
    `<baud_rate>'
          Usually 300, 1200, 9600 or 19200. This affects transmission
          as well as receive speed.

    `cs8 or cs7'
          Specify the transmission of eight (or seven) bits per byte.

    `ixon or -ixon'
          Enables (or disables) software flow-control (CTRL-S/CTRL-Q)
          for sending data.

    `ixoff or -ixoff'
          Enables (or disables) software flow-control for receiving
          data.

    `istrip or -istrip'
          Clear (or keep) the eight bit in each received byte.

     You may want to specify as many of these options as applicable.
     Unspecified options cause the terminal driver to make up the
     parameter values of the connection. These values are system
     dependant and may be in defaults or values saved from a previous
     connection.

     For tty windows, the `info' command shows some of the modem
     control lines in the status line.  These may include `RTS', `CTS',
     `DTR', `CD' and more. This depends rather on on the available
     `ioctl()''s and system header files than on the physical
     capabilities of the serial board.  The name of a logical low
     (inactive) signal is preceded by an exclamation mark (`!'),
     otherwise the signal is logical high (active).  Unsupported but
     shown signals are usually shown low.  When the `CLOCAL' status bit
     is true, the whole set of modem signals is placed inside curly
     braces (`{' and `}').  When the `CRTSCTS' or `TIOCSOFTCAR' bit is
     true, the signals `CTS' or `CD' are shown in parenthesis,
     respectively.

     For tty windows, the command `break' causes the Data transmission
     line (TxD) to go low for a specified period of time. This is
     expected to be interpreted as break signal on the other side.  No
     data is sent and no modem control line is changed when a `break'
     is issued.