cyrus torros wrote:
Given that CDE has been given many a modern patch and is now used on beefy machines mostly, how is its resource use?
I can't speak to the bleeding edge versions of CDE as I'm still running version 2.2.3, well before the switch to the autotools build system. Why haven't I upgraded? Because for me, it does what I need it to. That said: In 2015 I ran CDE 2.2.3 on an old ThinkPad Pentium III 1.0 GHz with 1 GB RAM (32-bit system) on Slackware Linux. I ran 4 virtual desktops, lots of dtterms, firefox, seamonkey, etc. all without any issues. That system was recently "retired" due to aging hardware. At one point I also ran CDE (probably same version) on the same ThinkPad running FreeBSD 9.x with no issues. I used whatever version that was in the FreeBSD ports/binary packages at that time. I'm currently running CDE 2.2.3 on a desktop Pentium 4 3.0 GHz with 4 GB RAM (64-bit system) on a highly modified/updated version of Slackware Linux. I built CDE from source. The system is from about 2005 and I have no issues. I am able to run multiple copies and versions of web browsers (firefox, seamonkey), watch youtube videos, and run audacity all at the same time. I would think CDE itself should run OK on your machine. The 512 MB RAM limit is definitely going to be a problem if you plan to run a modern web browser or an huge IDE like Eclipse though. How does the stock fvwm desktop perform on your machine? Are there other processes or daemons running that you don't need that you can shutdown? _______________________________________________ cdesktopenv-devel mailing list cdesktopenv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
