I've seen criticisms of the new release, 12.0, here and there, which is predictable. My question is a simple one: Is 12.0 just as stable, quick, and "Slackware" as, say 11.0?

The closest example I can think of is Gentoo: Many Gentoo users think that the 2007 release is awful, buggy, etc. and that users would be better to use an older install disc.

My answer is currently: "No". The only troubles I had were strictly kernel and hadware related, the rest of the distribution works well so far.

The only changes I've noticed are in HAL, like using CD's and my digital camera is taking some getting used to. The only real difficulties I've had were in trying to get it to do things that are new features, like use Compiz. I decided that I didn't really care anyway, so I'm back to just using it.

Smells like Slackware to me.

Joel

HAL is the default device manager?

I'm on slack 11.0 and 12.0 on my 2 PCs:
On the LapTop i use triple-boot - one is for testing (eg -current) and now it has a 12.0 on it
On the homePC (quad-boot) I also have a testing OS...
The impressions 12.0 vs 11.0:
The OS is rock-solid as expected... the bugs are really minor.
The software is extremely fresh and that makes problems (as allways)

the cons (Re: freshness):
gcc is 4.1.2 so forget compiling anything in beta (VirtualBOX or VMware or so...) until workarounds and fixes come...
slackpkg is missing due to mentioned freshness...

The homePC is actually a X2 Athlon and here is a suprise:
When booting with framebuffer console and the Tux logo enabled, there are two of them! is this a gimmick for SMP and multi CPU machines or a bug?

Conclusion:
we have two (2) choices:
1. Wait until someone fixes up for gcc 4.x and makes the packages
2. Dig until we fix, and make the packages, howtos or tricks available here ...

i guess it's really a matter of habit. some things have changed "under the hood" (and some people don't read CHANGES_AND_HINTS either)


#pinguins = #cpus - been that way, like, forever

I haven't forgotten my HAL question, but I have another: Will Slackbook, 2nd Edition, be current and completely accurate for this release? Last Slackbook update was about eight months ago.

HAL is the hardware abstraction layer.


it could use an overhaul, but it's still readworthy. Anyone to step up and do it ?

The main thing that put me off at first is the lack of checkinstall. I like to compile lots of custom packages. I later found out that checkinstall will work with the --fstrans=no option, so things are ok.

The gcc thing is a little annoying as well. Couldn't compile TVtime because of that. Had to download a prebuilt package from linuxpackages.net ... ugh

In general though, I am loving slack 12. HAL is great. It still feels lighting fast. Long live Slackware!

BTW: I did a fresh install of current, and when 12 came out, I "upgraded" to 12. Everything seems fine and I have checked that all the packages are there with slackpkg install-new. The only thing that could be a problem is aaa_elflibs. The package doc clearly states that upgrading is a bad idea:
Can I stay at aaa_elflibs-12.0.0-i486-2 safely instead of aaa_elflibs-12.0.0-i486-3 ?

a/aaa_elflibs-12.0.0-i486-3.tgz: Fixed a bad link in the install script. I
think the first-boot ldconfig would fix it anyway, but we like things clean
around here. Thanks to Robert Boucher for noticing this.

yes.

"ok, like, thanks."

But I was actually looking for a little more info...

What is this I hear about GCC? I really, really don't want to be using Slack for the first time and have half of my sources unable to build. It would be a sad experience. Is the issue that severe? Could someone please explain how Slack users are affected, etc?

I did not see troubles with my sources compiling under Slack 12's gcc (this might be because I use Slack as a desktop). However, I have some stability issues, especially related to X11.

Hi,
To the OP post #1.

Did you read the Slackware 12.0 CHANGES_AND_HINTS.TXT, UPGRADE.TXT and RELEASE_NOTES?

I find that the new release of Slackware 12.0 to be very stable. Sure, I've had some small minor issues but nothing that couldn't be repaired.

Most of the problems that I find from posts here on LQ are 'user' related. They fail to read the above documents therefore causing themselves a lot of wasted time.

Other than newbie problems like failing to burn the iso image or not checking the iso .md5 check. Bad burns and then blame the distribution.

Heck, PV & team are doing a great job! They can't go out and hold hands to make sure that everyone reads the documentation or make an effort to find an answer to the problem that they created.

'This a general statement not to alienate anyone but help'

READ, READ and READ more reference before you start to blame someone or something else for the problem. There are loads of information available to you too understand a subject.

You can cull the answer 'grasshopper' if you just know where to look. Open your eyes! Your on the inet so a google, LQ or even reference 'Slackware-Links' formerly 'Slackware LQ Suggestions Links!' for some good online reference.

Edit: correct my insert mistake, I work offline sometimes. The edit/copy/paste selection didn't include the OP.

Hi Gary, I was just asking to get a quick impression. I'll be reading readmes, changelogs, how-tos, and the SlackBook before I go for it. In the meantime, I'm warming up in Vector, although this distro's very well configured.