From what my brain housing groups understands, technically, yes.

So long as you constantly sync to the Changelog (i.e. keep up to date with changes) you will be always running the current development branch which will for a short time be the same as a stable release. The easiest way of achieving this I think is to mirror the tree and rsync it when changes occur. Then updgradepkg when needed keeping an eye on the Changelog.txt for possible gotchas.

Yes, and you'll have a lot of "fun" with it.
Running -current is not for everyone and definitely not for production systems or a desktop you really rely on.

Things *do* stop working once in a while, you might even encounter problems booting your installation, etc.
I run -current on two systems (one desktop and one notebook) to test new features etc. But my main computer runs the stable version, so that I can always access the internet, pay my bills, read my mail, download patches, etc.
If you are willing to test new versions, running -current is very interesting and your feedback can help other users and the Slackware team to make an even better product.
But if you want stability, stick with the stable version.

Hi all,

The Slackware store still shows 12.1. Is is possible to get the disks for 12.2 from the store yet?

Thanks,

-Drew

Use the Pre-order for 12.2, I assume that will work.

Do the subscriptions first get shipped within the U.S. then to Europe and beyond or is it the other way around?

OK.
I will contunue with the -current.
And if i got problem, i alwais have another partition with Linux ...

For me, upgrading is the easy way. If I were to reinstall, I would repartition my drive (right now I'm wasting space and I've been meaning to do that for a while -- actually since before 12.1 came out...). Also, I would have to recompile all of my third-party apps (I am pressed for time right now, so I will probably only recompile anything that breaks -- if anything). I keep SlackBuilds for everything, so it wouldn't be *too* bad, but it would still take a long time. I would also use a LUKS/LVM setup if I actually reinstalled, and I would have to read up on that since I've never done it before. Unless I kept my /home partition I would have to copy it from a backup post-install (but keeping the partition handy would be the easy way). All in all, I think after reading UPGRADE.TXT and CHANGES_AND_HINTS.TXT, it seems like a very straightforward upgrade (simpler than 12.0 to 12.1 perhaps), and I don't think it would take much time. But I could be wrong.

Since 10.2 (my first use of Slackware), I have upgraded to the next level by doing a fresh install.

For 12.2, I made an incremental upgrade because it seemed quite simple when I read UPGRADE.TXT and CHANGES_AND_HINTS.TXT.

So I agree with T3slider. This upgrade from 12.1 to 12.2 is no big deal (as long as you read the documentation).

Yes, I agree, after reading the UPGRADE.TXT, the procedure does look simpler than the 12.0 to 12.1 upgrade. I might give it a try this time.

12.2 up and running:-) All is good:-)

Ditto... now I just need to install my packages and tweak.

copied from Slackware page :) ;)
cheeers to lq slackware forum

so is anyone using kde4 on their new shiny 12.2 slackware ?

Trying to get it to work on gentoo laptop but the steps you have to go through on that to get it working is unreal - so i may put slackware back on there, but just wondering hows the performance of it ?

I still haven't made my mind up whether to install 12.2 or stick with 12.1. :scratch: