So, hey WiseDraco
I have a few slack 13/13ish setups going on
I wanted to test how slack would run if I added many pkg's from many repo's
obviously being careful
So, I installed Official 13, and then SalixOS, and Absolute 13.0.8
and both SalixOS and Absolute are 13 based.
Anyway, on my reg slack install I grabbed sbopkg, src2pkg, gslapt, and slackpack
just to see whats what
I also included every repo I could find to add to gslapt
heres my /etc/slapt-getrc
so, I have already added and subtracted many things from my test slack install
I haven't broken anything yet...
With all of my slackish installs I quickly got rid of XDM (salix) and GDM (absolute), replacing them with Slim from the Salix repo(comes with many themes)
and then setup Slim to run XFCE4(salix) and Icewm(absolute).
Slim is awesome and runs at much lower ram/cpu usage than either xdm or gdm
and Slim allows autologin for user and root, xdm/gdm cant do that.
With Salix I added Slackpkg, a bunch of apps from absolute and slacky repos
then I rebooted into runlevel 3, did slackpkg update && slackpkg upgrade-all
and after upgrading everything it could I rebooted and everythings Groovy
no problems dude
With my testbed pure slack install I added all kinds of stuff, then I compiled the source kernel as the hugesmp.s kernel doesn't have (MK7) checked, so I thought I should compile the kernel for my CPU.
It worked flawlessly since, runs at about 20mb less ram with firefox running
and the cpu usage has gone down a bit too.
As I write this I am compiling a kernel for my Absolute 13.0.8 setup
I went and got the 184.108.40.206 kernel source from here
absolute runs on 220.127.116.11 kernel (hell yeah)
its been twirling along for about 2 hours now
I think the pure slack 18.104.22.168 kernel took about an hour and half or so...
Absolute comes with OpenOffice and more
SalixOS even has a Livecd thats installable too
so, have fun with it