All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>,
	Josh Huber <huber@mclx.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: LinuxPPC X Server
Date: Wed, 02 Aug 2000 01:25:51 +0100	[thread overview]
Message-ID: <200008020026.BAA22003@hyperion.valhalla.net> (raw)


>> > However, 300M G3, UW SCSI + 256 Mb RAM ==> 6.5-ish Hours (*all* day was
only
>> > a slight exaggeration :-).
>> >
>> > (OK, so I did a kernel build as well [30 mins] and had a screen saver
>> > running - but... )
>>
>> I'm guessing that your screen saver might have been using a bit much
>> CPU.  I built XF4 on my powerbook wallstreet 233 in a little under 2
>> hours, with no configuration file changes. (except for ProjectRoot).
>
> Similar here on a Lombard 400 MHz - 1.5 hours, with ProjectRoot on a NFS
> mount. Only 64 MB RAM, only config file change was not to build fonts.
>
> The screen saver must have been running at over 60% CPU :-)

Which is rather worrying (seti screensaver runs very nice-d)  and I wasn't
using the graphics output...

Ho Hum... :-)

Hey, I'll try it again (with the correct config.) sometime soon...

Iain.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2000-08-02  0:25 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-02  0:25 Iain Sandoe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-08-02 16:07 LinuxPPC X Server Jack Howarth
2000-08-03 13:27 ` Kostas Gewrgiou
2000-07-31 14:07 Benjamin Herrenschmidt
2000-08-01 19:05 ` Michel Dänzer
     [not found]   ` <20000801191739.26835@mailhost.mipsys.com>
2000-08-01 19:37     ` Michel Dänzer
     [not found]       ` <20000801204113.29901@mailhost.mipsys.com>
2000-08-01 21:31         ` Michel Dänzer
2000-08-02 12:45           ` Geert Uytterhoeven
2000-08-02 23:27             ` Michel Dänzer
2000-07-30 21:24 Iain Sandoe
2000-07-31 12:53 ` Josh Huber
2000-07-31 16:28   ` Michael Schmitz
2000-07-30 20:33 Iain Sandoe
2000-07-31  7:50 ` Michel Dänzer
2000-07-31  9:25   ` Steffen Haeuser
2000-07-31  8:47     ` Michel Dänzer
2000-07-31 10:05       ` Steffen Haeuser
2000-07-31  9:03         ` Michel Dänzer
2000-07-31 10:21           ` Steffen Haeuser
2000-08-01 12:54       ` Kostas Gewrgiou
2000-08-01 16:25         ` Steffen Haeuser
2000-08-01 21:06         ` Daniel Jacobowitz
2000-08-02  9:20           ` Michel Dänzer
2000-08-02 18:17           ` Kostas Gewrgiou
2000-07-30 20:00 Iain Sandoe
2000-07-30 18:14 ` Michel D nzer
2000-07-30 22:33   ` Steffen Haeuser
2000-07-31  3:12   ` Daniel Jacobowitz
2000-07-31  7:40     ` Michel Dänzer
2000-08-01 21:03       ` Daniel Jacobowitz
2000-07-31 16:05   ` Michael Schmitz
2000-08-02 10:40     ` Martin Costabel
2000-07-30 22:46 ` Steffen Haeuser
2000-07-30 16:56 Iain Sandoe
2000-07-30 19:29 ` Steffen Haeuser
2000-07-30 21:13 ` Timothy A. Seufert
2000-07-29 13:31 Steffen Haeuser
2000-07-29 22:55 ` Takashi Oe
2000-07-30 11:27   ` Steffen Haeuser
2000-07-30 11:54     ` Takashi Oe
2000-07-30 14:40       ` Steffen Haeuser
2000-07-30 14:41         ` Takashi Oe
2000-07-30 16:13           ` Steffen Haeuser

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=200008020026.BAA22003@hyperion.valhalla.net \
    --to=iain@sandoe.co.uk \
    --cc=huber@mclx.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=schmitz@opal.biophys.uni-duesseldorf.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.