home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!munnari.oz.au!bruce.cs.monash.edu.au!monu6!aurora.cc.monash.edu.au!andrewc
- From: andrewc@aurora.cc.monash.edu.au (Andrew J. Cosgriff !)
- Subject: Re: Can X run with only 4 megs RAM?
- Message-ID: <andrewc.724292380@aurora.cc.monash.edu.au>
- Sender: news@monu6.cc.monash.edu.au (Usenet system)
- Organization: Monash University, Melb., Australia.
- References: <dpn2.193.724200652@po.CWRU.Edu> <Dec.13.14.03.44.1992.2074@telerobo.rutgers.edu> <1992Dec13.220329.29739@mailer.cc.fsu.edu>
- Date: Mon, 14 Dec 1992 00:19:40 GMT
- Lines: 32
-
- jblaine@garnet.acns.fsu.edu (Jeff Blaine) writes:
-
- >I have a 386-25 with 4 megs and a 9 meg swap partition. It seems very
- >odd the responses that this question has been getting. People with nearly
- >the same configuration are having totally different circumstances come about
- >from running X.
-
- >One person said they could run 2 xterms, xconq, xman etc and the initial
- >person said they had 2 to 3 minutes lags between mouse movements.
- >I can open one xterm. If I open anything else at all, X starts swapping
- >massively to disk. I mean, unbearable lag if I open anything other than
- >an xterm. X seems to swap for a few minutes (lots of disk action) if
- >anything more than that one xterm is opened. Does anyone know what the
- >deal is with all of these different reports?
-
- Is this the new X or the old one ?
- I remember back when I had 4 megs (on a 386dx25) and just got linux going
- with 0.97pl2 MCC dist. + X (ie X 1.0) and, yep, just having XClock, XBiff
- going beside an Xterm made it unusable...
-
- But then Dad bought another 4meg, so I'm no longer really relevant to the
- thread now...
-
- Enjoy !
-
- Cos !
-
- --
- -------------------------------------------------------------------------------
- * Andrew J. Cosgriff ! * #include <std_witty_quote.h>
- #define HERE cc.monash.edu.au #include <std_disclaimer.h>
- Hassle me at : andrewc@aurora.HERE ; andrewc@lindblat.HERE ; cos@yoyo.HERE
-