01-15-2002
If I understand what you are trying to accomplish with your home computer... You have a unix server. May I ask what version of Unix are you using?
I am extremely familiar with connecting "dumb" terminals to Unix servers as well as PC's using terminal emulation software.
Your serial port speed on your Unix server must match the serial port speed you setup on your Windows PC. Normally 38400 is the max in which you would connect a "dumb" terminal since more than likely you are using a text based application. You must also have "login" running on the Unix serial port.
Give me more info as for the operating system. Also, check to see if you have a file in /etc named inittab and ttytype
send me the contents of these 2 files via email if you wish.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am trying to find out what I should install to provide internet access and browsing possibilities on multiple unix terminals. Can anybody help?
TNXS (5 Replies)
Discussion started by: Jigger
5 Replies
2. UNIX for Advanced & Expert Users
I just changed from windows NT to XP and I am no longer able
to connect to my unix system. I used to use hyper terminal -- which acts as dumb terminal to my main frame unix system. I think one of the options used to be "direct to comX". This option isn't listed now. I use a serial port and the... (2 Replies)
Discussion started by: michelle
2 Replies
3. UNIX for Dummies Questions & Answers
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
4. Programming
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
5. UNIX for Advanced & Expert Users
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... (25 Replies)
Discussion started by: Phobos
25 Replies
6. UNIX for Dummies Questions & Answers
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
7. UNIX for Advanced & Expert Users
Hi, I am working in huge environment, I do type commands from my terminal window repeadly in all same setup unix environments. I am looking some kind of a terminal emulator or some simple program that will help me?
basically if type command like 'ls' in one unix terminal window it should echo... (5 Replies)
Discussion started by: rgmekala
5 Replies
8. Hardware
I want to build a network, in this network there is only one PC and 50 terminals, 50 students can use this system to study UNIX/Linux.
In the old days, computer was very expensive, many scientists shared a computer with terminals, that means a terminal has no cpu, memory and hardisk.
In... (5 Replies)
Discussion started by: haixiao_liu
5 Replies
9. UNIX Desktop Questions & Answers
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
LEARN ABOUT DEBIAN
llogin
LLOGIN(1) General Commands Manual LLOGIN(1)
NAME
llogin - Connect to a LAT service
SYNOPSIS
llogin [options] service
Options:
[-dvcpblhQ] [-H node] [-R port] [-n name] [-w password | -W] [-q quit char]
DESCRIPTION
llogin connects your terminal to a LAT service via latd, the service name must be known to latd for this to work.
OPTIONS
-d Shows learned services. This is the same as latcp -d -l
-d -v Verbose form of -d. -v without -d is ignored.
-H <node>
Remote nodename. If the service is advertised by more than one node and you want to connect to a particular node then use this
switch. By default you will be connected to the node with the highest rating.
-R <port>
Connect to a specific port on (usually) a terminal server. This is the port NAME on the server and not the port number.
-c Do not convert typed LF to CR. By default the enter key generates LF and llogin converts it CR as it is the most generically useful
translation. This switch will cause the enter key to send LF instead. Occasionally useful for connecting to Unix consoles.
-b Convert typed DEL to BS. By default the DEL key (keyboard, top right usually) send DEL (ASCII 0x7f) to the remote system. This
switch will cause the DEL key to send BS (ASCII 8) instead. Useful for some Unix systems connected via terminal servers.
-l Convert output LF to VT. By default LF output is sent as CRLF which can cause output formatting problems. Changing this to VT should
preserve the output formatting on most devices or terminal emulators.
-q <char>
Change the quit character. By default CTRL-] will quit the terminal session. Entering a character after -q will cause CTRL-<char> to
be the quit character for that session. -q0 will disable the quit character. If you use the latter, make sure you are connecting to
a service that will disconnect you when you log out or you will have to kill llogin from another session to get out of it!
-Q Tells latd that the service you are connecting to is queued service and not a normal login service or port service. Unfortunately
latd cannot tell whether a remote service needs to be queued or not so the onus is on the user to specify this switch when connect-
ing to a queued service.
-n <name>
Sets the local connection name. By default this will be your local TTY name. In most cases this simply affects the display of the
terminal on the remote end so you shouldn't need to change it.
-w <password>
Sends the password for the service. Only needed for services that require a password for access. If the password given is "-" then
you will be prompted for a password and it will not be echoed. This avoids having passwords visible on the screen.
-W Prompts for the service password. This is the same as -w- (see above).
-p Tells llogin to connect to the device named instead of a LAT service. This would usually be a /dev/lat pseudo-terminal but could be
any other device you like really. This switch does not make the program useful as a terminal program because there is no way to set
any serial parameters, nor am I going to add them. This is just a convenient way to use the /dev/lat ports without the overhead of
programs such as minicom.
-h Displays a brief usage description. This is the same as invoking llogin without any parameters at all.
SEE ALSO
latcp(8), latd(8)
LAT utilities January 3 2002 LLOGIN(1)