Sponsored Content
Full Discussion: Multiple Terminals
Top Forums UNIX for Advanced & Expert Users Multiple Terminals Post 59821 by Phobos on Saturday 1st of January 2005 06:34:54 PM
Old 01-01-2005
Multiple Terminals

Dear Members,

I have aquired a load of old Wyse dumb terminals. I have a Linux system set up that I want to be the host for all of these. Now, I know these don't use cat5 or standard networking. They are all done through serial (com) ports. However, I researched this more and found a converter to switch it to go over cat5 and a special hub. I have set all of this up but I cannot get the Terminals to connect to the host properly. I know they are sending and recieving data, as symbols and such pop up. I have tried messing with the type (IE. vt100, etc), but to no avail. I always thought you could set these up and they would automatically be compatiable with a unix system as this was how it was done in the old days. It would be able to connect using TERM, as when you login at the box you open a terminal connection. Any suggestions or help would be great!

Thanks,
Phobos
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Making X terminals out of a PC

Well I was trying to configure an Old PC having Win 3.1 to speak X with my UNIX server . I looked at notes , Looks like Debian Linux gives a base tarball to help boot of a floppy and talk to the XDMCP server . Well I was just hoping if there are other open source tools out there which would... (1 Reply)
Discussion started by: DPAI
1 Replies

2. Programming

Pseudo Terminals

I need to spawn a number of foreground process by reading a configuration file. Each process needs some form of I/O. Hence I need to run it on different terminals. How it can be done programatically , i.e. , my module needs to find which terminal is not in use, then open it, execute the process... (2 Replies)
Discussion started by: S.P.Prasad
2 Replies

3. UNIX for Dummies Questions & Answers

view all others terminals

i'm responsible for maintenance at my place and would like to watch all terminals in front me.i log myself into one terminal, but would like to view copy of other's terminals visible to me, it is just like for audit/security watch. (2 Replies)
Discussion started by: vkandati
2 Replies

4. Shell Programming and Scripting

calling multiple terminals

I'd like to write a script that will call n number of terminals that will all ssh to X-server and automatically enter the same password. Unfortunately I'm not exactly sure what kind of commands would work for me here because when I call for gnome-terminal, a new terminal pops up and the old... (1 Reply)
Discussion started by: gelitini
1 Replies

5. Shell Programming and Scripting

running Multiple terminals/shells

Hi, I'm looking for a way to send commands through multiple shells/terminals (not sure which is proper syntax). Basically, I have to open 3 different shells/terminals and run separate parts of a program suite in each of them. I find this annoying. The commands I have to do are simple, and could... (1 Reply)
Discussion started by: Caradoc
1 Replies

6. Programming

Handling Multiple terminals

Hi, Basically I've written a game in ncurses that supports multiple players. Each player has a process associated with him which shares a segment of memory in which the player's structures are stored, and these structured are accessed by the 'server' program and handled there. The scope of the... (13 Replies)
Discussion started by: dgre0018
13 Replies

7. UNIX Desktop Questions & Answers

non-overlapping terminals

Hi Everyone! I was wondering if there's an easy way to have terminals (gnome-terminal for instance) be open in such a way that they're not overlapping each other? I suppose I could play around with the --geometry option but that would imply me checking whether a terminal is already at a given... (3 Replies)
Discussion started by: anthalamus
3 Replies

8. AIX

How to open multiple virtual terminals to a single LPAR

I just wondering if there are ways to open multiple virtual terminal to a single LPAR. After I have use putty to login to the VIOS. I will use mkvt -id <LPAR id> to open console but if my friend want to open 2 second one, it will say, VT already connected. IS there a way to work this around ? ... (1 Reply)
Discussion started by: wingcross
1 Replies

9. Shell Programming and Scripting

Automate an application using scripting, managing multiple terminals

Hi I am new to Ubuntu and Bash scripting. I am working on a project to give a demo on an SDN application to my class. I need some help in scripting to create the demo. Please help in case if you have any idea on what am asking. The demo uses a tool called mininet. I need just one script so... (2 Replies)
Discussion started by: anzal
2 Replies
QTERM(1)						      General Commands Manual							  QTERM(1)

NAME
qterm - Query Terminal SYNOPSIS
qterm [ +|-alt ] [ +|-always ] [ +|-longname ] [ +|-quiet ] [ +|-sent ] [ +|-timeout ] [ +|-usrtab ] [ +|-watch ] [ +|-systab ] [ -wait interval ] [ -file tabfile ] DESCRIPTION
Qterm is used to query a terminal to determine its name. This is done by sending a special sequence to the terminal, reading in a response, and comparing it against a table of possible responses. The ``name'' printed to standard output should be one found in the term- cap(5) (or terminfo(5) for System V systems) database. For csh(1) users, putting a line in your .login file such as: setenv TERM `qterm` should automagically set your terminal type. For sh(1) users, putting these lines in your .profile file should set your terminal type: TERM=`qterm` export TERM By default, qterm uses the system tab file /usr/local/lib/qtermtab to obtain information for querying terminals. OPTIONS
+alt Use the alternate string ``<ESCAPE>[c'' when asking the terminal to identify itself. This string is recognized by most ANSI compat- ible terminals. -alt Don't use the alternate string, but the string found in the tabfile being used. This is the default. +always Always send the terminal query string. Normally the query string is only sent if it differs from the last string sent. -always Only send the terminal query string if it differs from the last string sent. This is the default. -file tabfile Use <tabfile> to find information for querying the terminal. +longname Print only the long (verbose) terminal name. -longname Don't print the long (verbose) terminal name. This is the default. +quiet Be quiet and only print the terminal name to standard output. -quiet Don't be quiet and only print the terminal name to standard output. This is the default. +watch Watch the characters sent and recieved to the terminal. -watch Don't watch the characters sent and recieved to the terminal. This is the default. +timeout Wait for timeout when listening for response string. This is useful if the first entry in a qtermtab doesn't have a response string with an ending character that is common with the rest of the qtermtab entries. -timeout Disable waiting for timeout when listening for response string. This is the default. +usrtab Use $HOME/.qtermtab to find information for querying the terminal. -usrtab Don't use $HOME/.qtermtab to find information for querying the terminal. This is the default. +sent Display the final response sent from the terminal in a ``nice'' fashion. -sent Don't display the final response sent from the terminal. This is the default. +systab Use /usr/local/lib/qtermtab to find information for querying the terminal. This is the default -systab Don't use system tab file to find information for querying the terminal. -wait interval Set the wait (timeout) period to interval (in seconds). QTERMTAB
The format of the file $HOME/.qtermtab and qterm's system tab file /usr/local/lib/qtermtab, consists of four fields each seperated by white space (tabs and/or spaces). The first field is the string that should be used to query the terminal. The second field is the string to expect in response to the query. The third field is the terminal name (compatible with termcap(5)) to print to standard output. The fourth field is optional and may contain a description of the exact manufacturer and model name of the terminal to be used in a message printed to standard error. Blank lines or lines starting with the character ``#'' are ignored and may be used as comment lines. A character preceeded by a ``^'' is taken to mean the control character. (i.e. ``^['' is interpretted as an <ESCAPE>). Both the send and receive (first and second) fields may contain octal values preceeded by a `'. (i.e. <ESCAPE> can be represented by `33'.) The ``expect'' (second) field can be a regular expression denoted by a leading backslash (`'). i.e. "^[[123" matches the string "^[[123", whereas "^[[123]" matches "^[1" or "^[2" or "^[3". See ed(1) for regular expression information. Below is a sample file: # # QTerm File # ^[Z ^[[?1;1c vt100 A vt100 with STP ^[Z ^[[?1;2c vt100 ANSI/VT100 Clone ^[Z ^[[?1;3c vt100 A vt100 with AVO and STP ^[Z ^[[?1;4c vt100 A vt100 with GPO ^[Z ^[iBO z29 Zenith in Zenith Mode AUTHOR
Michael A. Cooper, University Computing Services, University of Southern California. FILES
/usr/local/lib/qtermtab - System table $HOME/.qtermtab - User's table /etc/termcap - termcap(5) database SEE ALSO
csh(1), ed(1), sh(1), termcap(5) DIAGNOSTICS
Terminal not recognized - defaults to dumb. QTerm did not receive a response from the terminal, or the response did not match any that qterm has stored internally. Use the +watch option to check to see which is the case. BUGS
Many terminals do not send a response at all. 6 November 1990 QTERM(1)
All times are GMT -4. The time now is 01:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy