Newly Released: Slackware Linux Essentials, 2d Ed. 21
VincenzoRomano writes to point out that as of a few days ago, "Slackware Linux has its second revision of the Slackware Linux Essentials book. It is a major revision of the the reference book for Slackware users and is now an official Slackware project.
Slackware Linux is the oldest and yet pretty active Linux distribution born from an idea by Patrick Volkerding and that turned 12 a few months ago. It follows the KISS(Keep it Simple, Stupid!) philosophy, which seems to be one of the reasons of its long life.
The book itself has been created by David Cantrell, Logan Johnson and Chris Lumens and is available both in printed (dead-tree) form and in electronic form (HTML/DocBook/PS/PDF). Whether your are a Slackware aficionado or not, the book deserves a look at least!"
Re:Who uses Slackware anyway? (Score:2, Funny)
Re:Who uses Slackware anyway? (Score:4, Insightful)
That was back in the day, when you had to read the Makefiles and add and remove the appropriate "-D" options to get all sorts of fun stuff. Slack was lots of fun. I'm really happy I cut my teeth on it, but goodness, I don't have the time to track security flaws any more. I'll happily let RedHat, Fedora Foundation, or Debian tell me when there is a patch I need to be worried about. I still hand hack all my config files. Sometimes, I hand hack the RedHat specific config files, but I still read all the scripts and know all the commands to boot strap a machine from scratch if I really need to.
Kirby
It was perhaps a "joke"? (Score:2)
You know, that was my thought for a small fraction of a second until I realized it was a joke...
Re:Who uses Slackware anyway? (Score:2, Informative)
Once on the security mailing list you get advised whenever a new package has been updated to fix some security hole, and then you can just upgradepkg from the new package, if you need to.
Re:Who uses Slackware anyway? (Score:1)
Doesn't lack package management (Score:1)
Contrary to what many people seem to think, Slackware does have package management. There is a very clear package format that should be followed when making all Slackware packages, and there are official tools for using them that Patrick wrote (installpkg, upgradepkg, removepkg, pkgtool, makepkg, explodepkg).
Perhaps what the author was getting at is the lack of dependency checking that Slackware default package management software does not implement. Swaret is a popular tool that does support dependency c
You have got to be kidding (Score:1)
Comment removed (Score:4, Informative)
*cries and cries* (Score:1)
I read through the page, and didn't see the links, and then posted on impulse.
Failure to recognize the links for what they were may be somehow related to my only getting two hours of sleep in the past day and a half.
Happy Birthday to Me! (Score:1)
Slackware Linux 10.1 & Slackware Essentials, 2nd $60
Got Slack? T-Shirt - Extra Large $16
Support for Linux, excellent educational material and the most efficient way to run a server, $priceless$
Its a bit expensive, compared to http://linuxfromscratch.org/ [linuxfromscratch.org]
but worthy nonetheless.
Homage? (Score:3)
Re:Um... (Score:1)
Re:Um... (Score:1)
If anything I am a Fedora aficionado. I've used Debian back in the day (1998) and Redhat as well with a little SuSE thrown in for good flavor over the years. Why should I look at a book speificially targeting Slackware when I am not an aficionado? Just curious...
Imagine how much cooler your personal distro history would sound if you added "then in 2005 I started using exclusively using Slackware, because doing so allowed me to lengthen my personal distro history."
Packages (Score:1)
Hey slackers, read if you compile from source (Score:1)