From: "Chris Peterson" <capeterson@visi.com>
To: <speakup@braille.uwo.ca>
Subject: Re: Screen and Speakup-1.0
Date: Sat, 2 Feb 2002 23:43:08 -0600 [thread overview]
Message-ID: <002101c1ac75$a9d404c0$6801030a@greatmachine> (raw)
In-Reply-To: <20020203110706.A6806@joana.gotss.net>
Okay, good info to know.
Thanks,
Chris
----- Original Message -----
From: "Kerry Hoath" <kerry@gotss.net>
To: <speakup@braille.uwo.ca>
Sent: Saturday, February 02, 2002 9:07 PM
Subject: Re: Screen and Speakup-1.0
> Because screen provides console locking code;
> you can detatch a screen and log out;
> screens can be re-attached from another machine or console;
> screen is multi-user; more than one person can use a screen session.
> Screen's termcap/terminfo is more customizable than the raw console
allowing status lines etc.
> Swap isn't wasted on getty processes running on termianls that are unused.
> If you look at top you will probably see 8 getty processes running on 8
consoles
> and although there is a lot of shared code the remainder ends up in swap
sooner or later
> if they remain unused. Also; screen doesn't use
> a pseudo tty until it is required; and hence
> saves on file descriptor usage. The default global limit
> is 4096
> descripters with 1024 per process.
>
> Regards, Kerry.
> On Sat, Feb 02, 2002 at 04:03:34PM -0600, Chris Peterson wrote:
> > Why would you run screen from the console? Why not just login more than
> > once?
> >
> > Chris
> >
> >
> >
> > ----- Original Message -----
> > From: "Dave Hunt" <wx1g@mediaone.net>
> > To: <speakup@braille.uwo.ca>
> > Sent: Saturday, February 02, 2002 3:46 PM
> > Subject: Screen and Speakup-1.0
> >
> >
> > > Hi all,
> > >
> > > I'm running Speakup 1.0 in kernel version 2.4.9-13, with a Doubletalk
LT
> > > synthesizer.
> > >
> > > I've noticed that running the Screen windowing thing causes lag in
speech,
> > > especially in Pine. Reading in Lynx is lagged to a lesser extent.
ANy
> > > idea what's going on here?
> > >
> > > -Dave
> > >
> > >
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > >
> > >
> >
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
> --
> Kerry Hoath: kerry@gotss.net kerry@gotss.eu.org or
kerry@gotss.spice.net.au
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
prev parent reply other threads:[~ UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
Dave Hunt
` Chris Peterson
` Kerry Hoath
` SuSE Distribution Ron Marriage
` Thomas Ward
` Cheryl Homiak
` Ron Marriage
` Gregory Nowak
` Chris Peterson [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='002101c1ac75$a9d404c0$6801030a@greatmachine' \
--to=capeterson@visi.com \
--cc=speakup@braille.uwo.ca \
/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).