As the subject states... slackware-current development has re-surfaced and you folks are all invited to the party.

See ftp://slackware.osuosl.org/pub/slack.../ChangeLog.txt for a first glimpse while the mirrors are being populated.

Cheers, Eric

Ta Eric :}

And thanks for all the great work you're putting into Slackware!

Very cool:-)
Thank you Eric for your hard work crafting our favourite OS!
We appreciate it a lot!

Thanks Eric

Reading...

Wow, that shows a LOT of hard work!
I also give my thanks to all concerned.

I noticed the 2.6.23.1 kernel is the choice for the moment in current. So much is going on with the kernel I'll have to research what's new and improved before I'll consider a jump from stable.

With this drop of slackware-current, you do get the very latest of the big guys (kernel, X.Org and KDE)... for instance, my problem is that Ati has not yet released a proper driver for X.Org 7.3 which works for the lower-end Radeon cards that I have in my laptops. The opensource 'radeon' driver does not work 100% OK with the new Compiz in -current.

Using slackware-current means you'll have a lot of fun getting your functionality the way you want it ;-)

If you just need a stable working desktop for your work, sticking to Slackware 12.0 (aka the most recent Slackware-stable) is the wise thing to do.

Eric

Another annoying bit is that the third party synaptics source won't compile against xorg-7.3, so those of us who like it will have to wait...

damn! and there was me wondering what to make a module or built in to new .23 kernel - when i could have used the .config from current still think i will hold off on the current tree this time around, bad enough with a windows desktop being unstable i dont want my slackware ones being the same

Now up and running Slackware-current.
Only two hassles:
1. Problem with nut between keyboard and chair that failed to notice the new pixman-0.9.5-i486-1.tgz package, so X would not start.
2. Needed to recompile the proprietary nVidia driver (NVIDIA-Linux-x86-100.14.19-pkg1.run)to suit my graphics card. The first time I did the compile I got two errors about symlinks, but upon repeating there were no errors.

Early days, but all OK to date.

Update on this - it's possible
http://www.linuxquestions.org/questi...rg-7.3-592525/

After updating to -current, I got this warning when starting X: "error opening security policy file /usr/lib/xserver/SecurityPolicy". The xorg-server-1.4 package created a symlink /usr/lib/xserver -> /etc/X11/xserver, but that directory does not exist and the
SecurityPolicy file is missing. Anybody else noticed this?

Not until now :-)
However, I found why it's missing, and it should be fixed soon.
Thanks!

I see that current changelog states:

<<<<
x/mesa-7.0.1-i486-1.tgz: Upgraded to Mesa 7.0.1.
Upgraded to X.Org 7.3 PLEASE NOTE: There are a few known problems with this release.
Please let us know if you have solutions to any of these.
1. xf86-video-vesa was not upgraded for the X.Org 7.3 release, and running Terminal or vte under KDE results in an X hang under KDE, or garbage in the terminal under XFce.
2. The following modules were not upgraded in the X.Org 7.3 release and no longer compile: mkcfm, xf86-input-acecad, xf86-input-dmc, xf86-input-void, xf86-video-glide, xf86-video-impact, and xf86-video-wsfb. Odds are good that due to the driver ABI change none of these are currently working.
>>>>

Does it mean that I will have troubles with terminal uder KDE ?
My IBM T23 laptop is equipped with Savage video card. Will these lacking modules (point 2) harm my desktop in any way ?

As of now I upgraded only to Kde 3.5.8 waiting for a positive reactions from those who upgraded all packages . . .

The savage driver isn't affected by this (not that the savage driver is very good anyway, if my memory serves correctly). The other things probably won't have an effect on you, and the only way the vesa problem will bother you is if you're using the default vesa driver for X *and* using Xfce's Terminal.