Migrated to another OS: Slamd64

I have a 2x core amd machine. It runs windows xp, slackware, slamd64 and sabayon.

Some free promotion might be in place here, since I have never financially supported the last three OSsss (operating system).

Slackware is the venerable, but highly relevant (to this day) OS based on GNU/Linux. It's a back-to-basics-type of OS. I doubt there is another OS that is more instructive on the workings of UNIX-type (System V) systems (that is based on Linux :).

Thanks Patrick Volkerding.

Note: BSD-people, drop it. I'm not listening.

Slamd64 is the project of Fred Emmot which is based on Slackware, but supporting x86_64 (amd) architectures. Hence the name. It's young, vibrant. And follows the Slackware way of things. Cheers, Fred.

Sabayon, I barely use, but I will once I have more free time on my hands. It's a gentoo-based system, extremely easy to use. All the batteries are included, that means to say many functionalities that require tweaking are already pre-configured, and are ready to go! It supports most of the games available to GNU/Linux. The project is an italian one, geographically, but they have won the hearts and minds of many libre gamers around the world. They support both x86 machines and x86_64 machines.

Ringraziamenti, tutti gli amici! (Thank you babelfish)

So why did I migrate from slackware to slamd64? The main reason is because of my need/greed for speed. I have noticed that apps do react to events, and process tasks much more quickly on slamd64 than slackware. Also, slamd64 retains the freedom for tweakage as slackware does. I have found that migrating my /etc files is easy, since slamd64 follows slackware closely in how the system is laid out.

I shall build my erlang based cms on this platform now. This should have little to no unintended drawbacks to the project, since the erlang code itself does not depend on the architecture/platform where it is built. The erlang-interpreter is a different story though.
Mental note: blog that "different" story