Spotlight on Linux: Slackware Linux 13.1
People sometimes ask which distribution to try if they want to learn how Linux works. Common answers are Gentoo, Arch, or Debian. However, I disagree. Each of these distros teach users their particular brand of Linux. There's only one truly pure Linux, and that is Slackware.
Slackware is the oldest surviving Linux distribution. In its early years, Patrick Volkerdin rolled up a kernel, init, libraries, desktop, and applications to make Linux easier for users. And that's still what he is doing today. He doesn't change anything, he doesn't customize anything. Every component is exactly how the original developers intended. For example, users get a vanilla kernel and default desktop configuration.
Version 13.1 was released May 25 with Linux 22.214.171.124 and KDE 4.4.3. Slackware ships with other desktop options, such as Xfce 4.6.1, and lots of handy software. As expected, it comes with Web browsers, office applications, multimedia software, personal communication tools, image management, and more. Slack usually includes Java, but most other browser plugins and multimedia codecs are left to the user to install. 13.1 still uses HAL and udev in order to grant users access to removable media without root privileges or sudo. Along those same lines, this release also brings ConsoleKit and PolicyKit to allow even more convenience in running the system without elevated permissions. This release should be easy to use for users of any experience.
Slackware's original package management system - or software installer and uninstaller - neither resolves dependencies nor downloads from online repositories. However, some third-party attempts came along to address this and one, slackpkg, has recently been added to Slackware to bring the same capabilities as APT on Debian and Debian-based distributions. However, if you install the full range of packages on the Slackware install DVD, there isn't much extra on official mirrors. That's why some recommend the community repository hosted by slackbuilds.org. Between slackpkg and slackbuilds, Slackware has moved into the 21st century of software management.
Once upon a time Slackware was a favorite because of its hardware configuration method. In the tradition of keeping it simple, it had one file that users needed to edit (for most purposes). Most drivers were listed and users just uncommented whichever was used by their hardware. But even that isn't necessary anymore. Just like any other distro today, most hardware is automagically detected and configured.
Finally, the installer is another area of Slackware that gets some negative comments from time to time. It isn't very pretty by today's standards and it is keyboard driven, but it isn't difficult to use. It asks a few questions during the process in a similar manner as other Linux installers. Perhaps the most difficult aspect is the need to partition your disk prior to beginning the install setup. The installer disk comes with fdisk and cfdisk for this purpose.
So, all in all, besides the partitioning requirement and the lack of multimedia support, Slackware is just as up-to-date and easy-to-use as any Linux distribution. Like a split personality, today's Slackware is steeped in tradition yet surprisingly modern.
1. True Linux experience
2. High Performance
3. Extremely stable
1. Off-putting partitioning and installer
2. No live CD/DVD
3. Still uses Lilo for boot management
4. Lacks multimedia codecs
Susan Linton is a Linux writer and the owner of tuxmachines.org.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Tech Tip: Really Simple HTTP Server with Python
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Rogue Wave Software's Zend Server
- Parsing an RSS News Feed with a Bash Script
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide