It might be due to the fact that I am used to the ditto tool of QNX.
I am wondering if there is a tool that would allow me once in a SSH or Telnet session to have access to the TTY1 or TTY2 or TTY3 consoles.

I already found that VNC allows me to remote access to the X terminal but that is not what I am looking for. Since I control foreground programs running on the main TTY and that I do not use the X environment.

It might be very obvious to some of you but I am really a at This.
Thanks..

I don't really understand your question.

"Since I control foreground programs running on the main TTY and that I do not use the X environment." Please rephrase this.

SSH will give you a terminal just like TTY1,TTY2,etc. From there you can control any job.

If you mean you want to 'take over' what would be running on TTY1 if you were sitting at the computer, maybe you should look into running 'screen.' Screen allows you to detach terminal sessions (whatever jobs are running in that terminal) and attach them to other sessions. Type man screen at the command prompt.

Try to explain more precisely what it is you need to do.

Hello mac_phil
Thanks for your reply.

When I connect via a remote session ( telnet, ssh, )
I get the terminal "/dev/pts/0" from There, what I am trying to do is to have control over a specific TTY such as /dev/tty1 /dev/tty2, etc...

The screen command you are suggesting is interesting and seems very near from what I am looking for. So far I tried reading a lot but did not find a way to even see what is going on the /dev/tty1. I might just not know how to do it using the screen command so far

And getting control over a task running at another terminal is not what I am looking for because The program running at /dev/tty1 for example generates output at that terminal, which I want to see. Also I want to be able to stop the command and start it back at that same terminal. And I need to do so because it is not a daemon or a program that I want to run in background, and I do not want it to be killed once I exit my remote session.

Thank you for your interest in my problem so far

Right, sounds like you want screen. Whatever is outputting to tty1 should be run under screen. Then you can detach the screen session and later attach it to any ssh or tty* session. Now this valuable output is sent to a job which is not tied to any terminal.

Google for 'screen user's manual.' Read it all. You need to figure out how to run this program under screen, detach it, and attach it. I don't use that functionality of screen but you'll figure it out.

Think about screen as a full screen window manager for the command line. Only the whole window manager session can be made to disappear visually while it continues to run. Then the whole window manager session can be viewed later from any shell.

Basic intro:
screen - start screen(basically just gives you a shell)
ctrl-a - prefix for most screen commands
ctrl-a c - open a new shell/window
ctrl-a " - see list of shell windows(numbered)

OK I had a minute to play with screen and here is how you do it.

Shut down whatever is generating that output.
<screen> - starts screen
<command-to-start-that-program> - start generating output
CTRL-a d - detach session

Then, when you want to look at that output via ssh or whatever
<screen -r> - reattach session