01-01-2005
Well, these terminals don't use standard networking. These are all done with serial connections. There is no ip address, no MAC address, no nothing. It would be like connecting two computers via com ports except the terminals are just dumb terminals all they include is screen, keyboard, and two com ports (one for printer and one for data). This stuff is pretty old school, but still interesting!
Last edited by Phobos; 01-01-2005 at 09:24 PM..
9 More Discussions You Might Find Interesting
1. 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
2. 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
3. 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
4. Shell Programming and Scripting
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
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
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
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
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
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
LEARN ABOUT SUSE
aconnect
aconnect(1) General Commands Manual aconnect(1)
NAME
aconnect - ALSA sequencer connection manager
SYNOPSIS
aconnect [-d] [-options] sender receiver
aconnect -i|-o [-options]
aconnect -x
DESCRIPTION
aconnect is a utility to connect and disconnect two existing ports on ALSA sequencer system. The ports with the arbitrary subscription
permission, such as created by aseqview(1), can be connected to any (MIDI) device ports using aconnect. For example, to connect from port
64:0 to 65:0, run as follows:
% aconnect 64:0 65:0
The connection is one-way, and the whole data to the sender port (64:0) is redirected to the receiver port (65:0). When another port (e.g.
65:1) is attached to the same sender port, the data is sent to both receiver ports. For disconnection, use -d option.
% aconnect -d 64:0 65:0
The address can be given using the client's name.
% aconnect External:0 Emu8000:1
Then the port 0 of the client matching with the string "External" is connected to the port 1 of the client matching with the "Emu8000".
Another function of aconnect is to list the present ports on the given condition. The input ports, which may become sender ports, can be
listed with -i option.
% aconnect -i
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 64: 'External MIDI-0' [type=kernel]
0 'MIDI 0-0 '
Similarly, to see the output ports, use -o flag.
You can remove all existing exported connections using -x option. This function is useful for terminating the ALSA drivers, because the
modules with sequencer connections cannot be unloaded unless their connections are removed.
OPTIONS
CONNECTION MANAGEMENT
-d, --disconnect
Disconnect the given subscription.
-e, --exclusive
Connect ports with exclusive mode. Both sender and receiver ports can be no longer connected by any other ports.
-r, --real queue
Convert time-stamps of event packets to the current value of the given real-time queue. This is option is, however, not so useful,
since the receiver port must use (not necessarily own) the specified queue.
-t, --tick queue
Like -r option, but time-stamps are converted to the current value of the given tick queue.
LIST PORTS
-i, --input
List existing input (readable) ports. This option is exclusive to -o.
-o, --output
List existing output (writable) ports. This option is exclusive to -i.
-l, --list
List the current connection status. The connected and connecting ports from/to each port are listed together. The suffix flag [ex]
means the connection is exclusive. The suffix flag [real:#] and [tick:#] mean the connection includes real-time and tick conversion
on the listed queue, respectively.
REMOVE ALL CONNECTIONS
-x, --removeall
Remove all exported connections.
SEE ALSO
aseqnet(1), aseqview(1)
AUTHOR
Takashi Iwai <tiwai@suse.de>
August 31, 2000 aconnect(1)