From: Mario Lang <mlang@teleweb.at>
To: blinux-list@redhat.com
Subject: Re: Screen Command vs. Virtual Consoles
Date: Sat, 23 Mar 2002 21:33:15 +0100 [thread overview]
Message-ID: <87elib6n3o.fsf@lexx.delysid.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0203231003400.7287-100000@localhost.localdomain> ("John J. Boyer"'s message of "Sat, 23 Mar 2002 10:08:46 -0600 (CST)")
"John J. Boyer" <director@chpi.org> writes:
> Is there any advantage of using the screen command over using virtual
> consoles?
You can detach and later reattach to screen sessions. This allows
me to leave certain programs running, and reattach to their screen
instance when connecting later.
Imagine, your computer has a network connection reachable from the internet
say, via ssh. You login locally on your virtual terminal or whatever you use,
and start screen. Then you open several screen windows, and start programs
in there, say, e.g. Emacs, a shell session, and a lynx session.
Now you have to leave your computer, you can either leave screen running, or
for safety, detach the session using C-a d.
Now you login into that machine from somewhere else, e.g. you went to work.
You can invoke screen -r or screen -dR to reattach to the detached session.
You get the same state as you detached it. See man screen for a description
of the various detach/reattach commands.
It is also possible to have screen as your login shell, basicly giving
you a simultaneous session for each login.
Also, you can attach to a running screen session without detaching the
other terminal. Thats the option -x, and allows two
or more people on different terminals to work with the same programs. I used
this technique for a Linux course for blind students to replace
overhead alike mechanisms. They simply all attached to my screen session.
This helped extremely much.
The method even worked the other way round, I configured their logins in such a way
so that they were in a screen session everytime. So if someone had a problem,
I simply attached to his screen session, and could see what was on his screen
without having to move physically and disturb him by using his braille display.
Recently, I also discovered that you can use screen to attach to a
pty, a pseudo terminal. The only real world use currently I know of
is to connect to certain ptys created by User-mode-linux.
--
CYa,
Mario
prev parent reply other threads:[~ UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
John J. Boyer
` Mike Gorse
` Cheryl Homiak
` Dave Mielke
` Cheryl Homiak
` Dave Mielke
` Janina Sajka
` Mario Lang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87elib6n3o.fsf@lexx.delysid.org \
--to=mlang@teleweb.at \
--cc=blinux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).