Slackware 12.2 is released Officially
 

Yes folks, 'tis the season to announce a new release of Slackware. With a shiny new kernel, many package updates, and the newly added ability to install from a Samba share, we bring to you the latest in the stable Slackware 12.x series. Slackware 12.2 ships with the 2.6.27.7 Linux kernel, the Xorg 1.4.2 X server (with many driver, library, and application updates), Xfce 4.4.3, KDE 3.5.10, simplified wired and wireless networking with wicd in /extra, package upgrade management with slackpkg moved into the main tree, support for non-usb-storage digital cameras through libgphoto2, pm-utils (tools to support suspend and hibernate through HAL), and much, much more. This release brings the system up-to-date without compromising stability or compatibility with the 12.x series.

Link to the full announcement:- http://slackware.com/announce/12.2.php

This is excellent news now how do i tell the wife what iam doing at the weekend,i believe its christmas shopping or an install of 12.2.

(christmas shopping it is then lol)


regards

todders

Get your priorities straight man! New OS is always the priority (hehe)

yea i know but i dont mind admitting on here i don`t wear the trousers in my house!!!!

if my wife is happy so am i lol


a receipe for a happy life i believe

todders

My guess is you both wear trousers but that you are now and then interested in getting hers off. ;) :D

woodsman good point but iam 41 years old now a cup of tea and a digestive are more my style these days...

Has anyone ever used slackupdate:

to upgrade from xx.x to xx.x+1?

The beta claims to have the ability to do so (marked EXPERIMENTAL!), so I'm curious as to whether anyone has attempted to go this route.

(cowers in corner expecting 1000 posters to admonish him for even considering this shortcut....)

cheers,

I can't believe how fast the transition was between 12.2-rc1 and 12.2 being fully released. Apparently, the transition from 12.1 to 12.2 was much smoother than 12.0 to 12.1. Maybe I'll actually decide to install fresh instead of taking the lazy upgrading route this time (but only time will tell that -- I'm pretty lazy, so I may just upgrade and hold off reinstalling).

Caught me by surprise...
I noticed that my rsync pulled down a patch-2.6.27.8 file today in the K source directory, so I wasn't expecting the release as I'd not seen a kernel bump in the changelog.

There seems to be a lot of filesystem related stuff in the .8 changelog, mostly for ext3/4. I might as well build a .8 kernel from it seeing as i've got the patch already. :)


Anyway, Big congratulations and thanks go out to the team. :)

Congratulations, Mr.V:-) Wonderful news!

mrclisdue i haven`t used it to be honest,but i can see huge tears before bedtime if it goes wrong :-) the upgrade path from 12.1 to 12.2 looks fairly easy and straight forward this time i would always use that a lot more fun than anything automatic.:-)

see ftp://slackware.osuosl.org/pub/slack....2/UPGRADE.TXT

Let us leave our bit torrent clients open as long as possible. I'm heading to the store to make a donation. Okay. Just made my donation.
Here's a link to the store if you'd like to donate.

http://store.slackware.com/cgi-bin/s...rrKw:mv_pc=495

Same same...............unemployed right now but I'll still donate to Slackware!!

Thank you, sir. I have always done it the *proper* way, previously, so I don't have any qualms about doing so....

cheers,

Downloading it now to replace my Ubuntu 8.04.1 install on my desktop.
I have been running 12.2RC on my laptop, and was having fun tweaking it; practicing for the final release. WOW... I wasn't expecting it to be out so soon... ;)

Damn, OSU mirror is fast. Got the DVD ISO in 39 minutes.................

I have been following -current on two different machines and it has been very stable. Like I said in another thread recently: it has been a bit 'dull', with nothing breaking ;)
Now that 12.2 has been declared stable, I'll update my other boxes over the next few days / weeks.

Off to the Slackware store now to order the DVD!!!
(but will also open a torrent and help seeding...)

Big thanks to Pat V and all the contributors here and elsewhere!

Great news, thanks to all :)

It's looking good so far!! I was going to hold off installing this latest release but after following the changelogs and the positive comments from the users of Current I said "what the hell." The only thing that I have noticed is that it takes a bit longer to boot up but I'll tinker with that in the morning.

The one thing I did differently on this install was to use JFS which I suspect may be causing some of the delay in booting up.

Don't forget to go to the Slackware store so Pat can feed the family!!

Thanks to the Slackware team for a job well done and a product that finished much sooner than expected!!

I always thought a fresh install was the lazy way (it's the route I usually take), as it seems to involve less work and less possible hitches than an upgrade.

What is the link of the OSU mirror?

Here is the OSU mirror:
http://slackware.oregonstate.edu/slackware-12.2-iso/
This mirror is really fast also:
http://slackware.mirrors.tds.net/pub...ware-12.2-iso/
Since you are outside the USA it may not be quite as fast for you though.
The torrents are really fast also; and you can help out by seeding the .isos if you can spare the bandwidth.

Very happy with 12.2 so far! Thanks to Pat V and the team!

Same here. This time I took a slightly different approach.
My system is setup with /boot on /dev/hda1 and an encrypted LVM on /dev/hda2 containing lv's for / /var /tmp /home.

What I did was create 2 new lv's for the new / and /var alongside my existing ones. Mount them under /mnt and then use installpkg -root /mnt to install all the filesets. Copy over /etc/fstab and edit as appropriate to use the new lv's. Copy over /etc/crypttab and my keyfiles for my secondary encrypted volume group. Add my users to the new passwd, shadow, group files etc.

Before I booted up off the new system, I chrooted into the new / and ran through some of post install setup steps in pkgtool just incase I'd missed something and built a new initrd for my LUKS/LVM setup.

Bob's your alien! I have 2 versions of slackware in 1 LVM setup.


Now, when I come to get rid of 12.1 all I have to do is remove the 2 old LVs and the lilo entry.

Though upgrading with the normal method is a little less involved, I get a clean install and a proven backout without the need to restore from backup.

This was the first time I tried this approach and a bit of an experiment, but it seems to have worked out quite well.

That's something else I haven't got round to reading about: LVM. I like that: "Bob's your alien!" :D

People in Europe could try
ftp://elektroni.phys.tut.fi/slackware-12.2-iso/

Getting the torrent and will be sure to leave it up...
Well, it will have to be limited as I don't think FSU likes me uploading at over 500kB/s :(

Hi,
I have added the following to 'So you want to be a Slacker! What do I do next?' sticky;

Mmm, it does sound quite a bit different to 12.1. Maybe I'll have it after all...Yes!

Excellent!! I'm downloading the iso right now and I'll install both at office and home tonight

Thak's P.V. for this awesome distro. :-D


Cheers

CDs burned this morning:-) Slackware 12.2 install fest coming up after work today:-)

Hi.
Stupid question :

If i continually run -current, does it mean i run the latest Slackware version?
Don't need to upgrade ? Never? :)

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:

take the plunge!!!

Hi,

Just like the bunny and Timex. Slackware just keeps on ticking!

I can't swim. :)

I don't believe you, even if you throw a baby in a pool it'll swim, a dog, a cat, a squirrel, they all quickly learn how to swim when thrown in water. I'm sure you will too.

@Carpo
I have a second partition that has KDE 4.1 from testing installed in place of KDE 3.5.10. It is a little slower to start up compared to KDE 3.5.10 ( although that is an impression as I have not actually timed it). In my limited experience KDE 4.1 is no different to KDE 3.5.10 in actual use as far as responsiveness is concerned. I am liking the the new program startup menu arrangement, which I think is good for getting to the most often used programs more easily.

I have not experienced any crashes although there have been some messages about unimplemented functionality and some weird display results when I have played with widgets, although that may be my inexperience more than KDE 4.1.

As is stated in the ChangeLog, there are still issues with some software.

Overall I like the new look, which makes 3.5.10 seem jaded.

My advice would be to clone your 12.2 install in a second partition, remove KDE 3.5.10 and install KDE 4.1 and have a play!