Post a Comment
I thoroughly enjoy using Slackware. It does exactly what I want it to do. It stays out of my way, and provides a nice stable system. The package management might not be as advanced as apt, but it does its job well.
As soon as I get around to getting an optical drive attached to my server, I'll be removing Ubuntu, and going back to Slackware!
I find it much quicker on the desktop too. That may not be entirely true, but it feels that way right now.
Long live Slackware! 
Hey guys and gals, I have a question. It was mentioned in the last Slackware thread that they do not support PAM. I've been using PAM extensively since I became a system administrator a few years ago, and I'm curious how much can be accomplished without it.
At work many of my machines authenticate LDAP users with kerberos passwords. The LDAP and kerberos databases are on different servers. Effectively, the /etc/passwd information comes from LDAP server X, while the /etc/shadow information comes from kerberos server Y. Is this possible with Slackware Linux (i.e. when not using PAM)?
PAM is a generally poor authentication method, since the documents one must use to base their implementation on are not good enough to ensure that all implementations are properly inter-operable. It's also a security risk, because of said badly made spec, Slackware doesn't carry it largely because of the security risks.
OpenBSD has no PAM support, and advises against it, and instead uses BSD authentication, which comes from BSD/OS.
Just because OpenBSD has no PAM, does not prevent one from compiling a PAM implementation (whichever is needed) and using it, the same can be said of Slackware.
There is a little bit of (dated) info on LDAP without PAM here: http://wombat.san-francisco.ca.us/faqomatic/cache/95.html
Edited 2007-07-03 02:31
I don't understand peoples' gripes about the 2.4 kernel. It's never been mandatory in Slackware and there have been 2.6 kernels on the CD for the past few versions. Just cos it's not the default, folks get the idea it's nto supported!
Meanwhile 2.4's been great for keeping my 8 year old PC going on. Choice: it's a good thing!
PS I'm not singling you out, that's "folks" plural 
But, IIRC, using a 2.6 kernel up to Slack 11.0 was somewhat and sometimes a little difficult (I recall now some fights with the modules for lm_sensors, for example).
And the use of a 2.6 kernel on current since a few months ago came without a hitch. Once PV makes his mind a change, he makes it thoroughly.
Besides that, on an old K6-2 450 128 MB RAM the 2.6 series felt even a little snappier than the 2.4 series.
I always install the latest version of Slackware when reinstalling because stability and performance have always improved, at least in the four years since I first installed version 9.0.
I tend to think that unless there is a very good reason to install a previous release such as better hardware support one should stick to the latest and greatest. There is no reason not to because this is not that other OS :-).
It's also very nice to run Slackware 12.0 x86, MIPS and ARM at the same time. Slackware is fast and stable regardless of the architecture it runs on, which attests to its excellent design.
More precisely I was talking of Slack 10.2, when managed to (sort of) make 2.6 work on it, video playing, for example, was smoother, and Quake 3 run better too.
That venerable and beloved K6-2 is still running 10.2, by the way... and when someone (wife, kids) takes control of the new PC, I surf the web on it (using Opera and IceWM+Rox among other low requirements software).
Making Direct download ISOs mirror(CDs only)...
http://proyectos.pixelamigo.com/software/slackware/12/iso/
Please be patient and not abuse.
Use bittorrent and give something back to the community!
http://www.slackware.com/torrents/
Perhaps you were just a little hasty. At the time of this writing, there are 1861 peers in the swarm...
Needless to say, download time is quite good.
Believe it or not, there are even 31 peers with 12 downloading on an old Slack-11 dvd image that I am still seeding...
Come to think of it, if you order the DVD with say, 24 hour delivery, the post office will manage a transfer rate of around 45 MBps (or ~360 Mbits/s)
Edited 2007-07-03 19:37
bring Microsoft closer to non-existence... at least in my home since I have installed the previous RC2 and loved it with XFCE. Slackware always just works the way I want. It hardly ever changes and when it does, it makes sense and seems like Pat did it for a good reason. I am going to really learn some package making this time around.
I used Slack for a couple years and I loved the stability and community. Over time I moved to Ubuntu because it was very user friendly. This 12.0 release announcement has me wanting to go back to Slack. Has anyone ever noticed how most distributions have comments where people have complaint after complaint and the vast majority of Slack comments praise it?? Long live Slack!
And thatīs because Slack is getting better every time, release after release. Iīve been on --current since three years ago, and progress can be felt, together with stability and speed.
In the same machine Iīve installed Slamd64 and Gentoo64 and I keep going back to Slack for everyday use.
Go Patrick, go!!!
long time slack user (since 2000), and i have to say that they've finally created something worthy of putting on my mac pro! on older hardware slackware runs great, on newer hardware because of the pathetic 2.4 default kernel in older versions (11.0 even), i couldn't get simple things my network card recognized.
great job pat!



