4 Mar
2012
4 Mar
'12
2:36 a.m.
On Sat, Mar 3, 2012 at 10:49 AM, /dev/ammo42 <mickeytintincolle(a)yahoo.fr>wrote;wrote:
On Sat, 3 Mar 2012 02:36:00 +0000
Tiago Marques <tiagomnm(a)gmail.com> wrote:
Not my experience in ANY way. Not even with Nepomuk and other "bloat
disabled". Still, 200MB is a huge amount, you won't be able to run almost
anything else and you won't have 256MB available either, so... tough.
Best regards
Raspberry Pi is the kind of device that can work
reasonably with
Trinity but not KDE4. Last time I checked I had Trinity running in
80MB for RAM while KDE4 was having trouble fitting in 600MB. For
people who asked about reasons to keep KDE3 alive in Trinity, I would
point to a working testbed, if we ever get to assemble one.
With a sane
configuration KDE SC 4 is not heavy. On my 32-bit Slackware
13.1, I had 200M used by the entire system. After firing up KDE4 from
another console with another user on another X server, I had 340M used,
still by the entire system. The Raspberry Pi having a good GPU and 256M
of RAM, I think KDE SC 4 can run without problem on it.
Best regards,
Tiago
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-devel-help(a)lists.pearsoncomputing.net
Read list messages on the web archive:
http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting