Using another OS system is certainly not a move I want to make. I am to pleased with Slackware in everyway to give up on it just because April 1st current tree is different from the previous years. You are right, current is not stable, nor is it instable either. Regardless if I were to wait until Slackware 12 is official, or get my feet wet while its being updated I would still be faced with the challenge of installing X in a manner that I would like to. Compiz is unstable, but, Pat has decided to include it in the x/ series for one reason or another. The changelog does read that Patrick is just getting his feet wet with compositing, so I did not hold high hopes or expectations of this branch. However, the concern about installing only what is needed can be applied to compiz and others as mentioned, but there is the lack of documentation to support an "easy" method of it.

hmm.. you should not ever move to another distro! ;-)

slackware is the best thing i've ever found to be installed on my PC :-)

slackware-current has last time been quite useable and as i've heard it's usually the like. but now there are numerous changes which deeply affect the whole distro. new gcc, new python, new xorg, new everything.

so you can experiment and struggle with such errors or wait patiently ;-)

I agree.

Really, I would try current if it were just a little more stable

The xserver package was upgraded, the previous package was a development release (as revealed by "Xorg -version"), this one is working much better, I have a usable resolution now =)

still no dice with ATI's drivers though...

I had done an upgrade to Slack-Current last week from a clean Slack-11.0 system, however it wasn't very stable, and some libraries were broken. I keep a local repo of both Slack 11 and current, and made an install DVD of current and installed it clean. It works perfect, and so far, I've not had any burps at all.

Regards,

D

I now have compiz working! I am not sure if it was the updates to current which helped, or the fact I was a little more patient with this go at it. I do have Xorg working without the entire x/ series. I would post what files I used, but I do not want to be held responsible for others broken systems :-) Anyway, if anyone may be interested I wrote down on paper which files excatly I used. It is certainly not the entire x/ series but it also may be incomplete. Just thought I'd give the update!

xorg, kde and compiz have been updated last night. i guess that gave you the boost ;-)

indeed. Slackware-Current is not intended for people who seeks for stability, but it's intended for developers/testers who would like to try out some new features that (probably) will be on the next release of Slackware, so don't expect everything to be stable while in -Current since everything can change in this phase

I managed to find a website that has a breif overview of some components of X. As I learned, my initial "minimal" install of X was not so complete as I was missing some of the core of Xorg. Thought I'd post this link incase anyone else may be interested..

http://www.stanford.edu/services/pubsw/package/x/

I do believe they only list what is used on their computers, and I am positive that they do not inlcude any of what is needed for Compiz (like libXcomposite and libXdamage). But it helped me get a complete base without the extra packages! Check it out, and lets hope it stays up for a while .

Check out my post at http://www.linuxquestions.org/questi...95#post2685195 for a small (not-so)-minimal X pkg requirements.

I have installed all the x packages but still having problems. Cannot even run xwmconfig. When I run xwmconfig I just get "Cancelled." printed on the screen.

Are you running it as root? If not do and enter the root password in a terminal window. It should work then.

I got it working in the end. The new version of bash doesn’t include some of the commands. The ones I have been able to find are “which” and “dialog”. I hit that problem while running swaret as it was saying that it needs pkgtool to run and I had pkgtools installed but when I looked at the script I realised it was using “which” and it wasn’t working so I had to install the “which” package. The had similar problem when running xwmconfig as it uses “dialog” which I had to install separately but one thing that is bit annoying is that it writes the error to an output file then delete it. So unless you amend the actual script you will never be able to know the error.

bash never has included those commands.
There's a reason that the Slackware mirror contains a file called UPGRADE.TXT - if you had read it, you would:
1) not have used swaret to do the upgrade
2) not have run into this problem

Only if you do the kitchen sink upgrade. "--install-new" is overkill but one does have to hunt down what pieces are missed with upgradepkg. Something in audacious wants ruby but works alright except for the error popup.