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 at mediaone.net> > To: <speakup at 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 at braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > -- Kerry Hoath: kerry at gotss.net kerry at gotss.eu.org or kerry at gotss.spice.net.au
