A KDE4 Operating System In Less Than 200MB

[tkmorris]

Still not faster than DWM...

The only thing I would like is upstream to provide/move to xcb, it takes almost 1s before I can open a terminal from cold boot, which doesn't happen with outdated xcb patches/forks or monsterwm-xcb

Maybe I could try solving it by mounting dwm with ramfs/tmpfs, but not probably since it's Xlib latency

[Awesomeness]

It actually is, ignoring the fact that your example is complete nonsense.

Did you really expect anything else from troll RealNC?

[boast]

Face it, KDE is a pig

for computers from the 90's...

[Rallos Zek]

Still not faster than DWM...

It is on my system.

[a user]

And DWM is not faster than Windows 3.1.

even gnome2 2d without effects is faster than win 3.1 de

[frign]

And DWM is not faster than Windows 3.1.

It actually is, ignoring the fact that your example is complete nonsense.

[RealNC]

Still not faster than DWM...

And DWM is not faster than Windows 3.1.

[frign]

As you can see by Tomas' post, KDE doesn't consume 180 mb. And KDE _is_ efficient, if you disable all effects it runs faster than DEs like LXDE(!).

Still not faster than DWM...

[Veerappan]

Actually, I answered that one so many times that I'm losing track who got the answer and who didn't
ARM version was planed for a while, but I discovered that it's not such universal as like x86. There are many ARM devices out there and each one (as far as I understand it) needs different firmware to boot. I can't possibly support all ARM devices, so I would have to pick just few, and that makes no sense to me.

Else it is actually pretty simple to make Slax for ARM, all sources are available on FTP and Slackware (which is base for Slax) already has official ARM version as well. Unfortunately I don't have any fast ARM device here, just some RaspberryPI which has just 256MB, it's not possible to recompile KDE4 on that... it needs around 4GB of RAM for compilation (yet it runs just fine on 256MB of RAM when compiled).

Building on ARM devices is a PITA, sometimes. I'd recommend checking out the various cross-compiling toolchains. I've used scratchbox2 for some cell-phone related Linux development in the past and it worked pretty well.

A quick google search actually turned up what looks to be a very relevant result (a how-to/script for apt-based distros which will set up scratchbox2, qemu, and a rootfs for raspberry pi cross-compiling):

http://pastebin.com/4Jp1WPTb

[TomasM]

So...how about to port it to ARM and my other questions ?

Actually, I answered that one so many times that I'm losing track who got the answer and who didn't
ARM version was planed for a while, but I discovered that it's not such universal as like x86. There are many ARM devices out there and each one (as far as I understand it) needs different firmware to boot. I can't possibly support all ARM devices, so I would have to pick just few, and that makes no sense to me.

Else it is actually pretty simple to make Slax for ARM, all sources are available on FTP and Slackware (which is base for Slax) already has official ARM version as well. Unfortunately I don't have any fast ARM device here, just some RaspberryPI which has just 256MB, it's not possible to recompile KDE4 on that... it needs around 4GB of RAM for compilation (yet it runs just fine on 256MB of RAM when compiled).