Slackware 14.1 released…
Yes, it is that time again! After well over a year of planning,
development, and testing, the Slackware Linux Project is proud to
announce the latest stable release of the longest running distribution
of the Linux operating system, Slackware version 14.1!
We are sure you’ll enjoy the many improvements. We’ve done our best to bring the latest technology to Slackware while still maintaining the stability and security that you have come to expect. Slackware is well known for its simplicity and the fact that we try to bring software to you in the condition that the authors intended.
Slackware 14.1 brings many updates and enhancements, among which you’ll find two of the most advanced desktop environments available today: Xfce 4.10.1, a fast and lightweight but visually appealing and easy to use desktop environment, and KDE 4.10.5, a recent stable release of the 4.10.x series of the award-winning KDE desktop environment. These desktops utilize udev, udisks, and udisks2, and many of the specifications from freedesktop.org which allow the system administrator to grant use of various hardware devices according to users’ group membership so that they will be able to use items such as USB flash sticks, USB cameras that appear like USB storage, portable hard drives, CD and DVD media, MP3 players, and more, all without requiring sudo, the mount or umount command. Just plug and play. Slackware’s desktop should be suitable for any level of Linux experience.
Slackware uses the 3.10.17 kernel bringing you advanced performance features such as journaling filesystems, SCSI and ATA RAID volume support, SATA support, Software RAID, LVM (the Logical Volume Manager), and encrypted filesystems. Kernel support for X DRI (the Direct Rendering Interface) brings high-speed hardware accelerated 3D graphics to Linux.
There are two kinds of kernels in Slackware. First there are the huge kernels, which contain support for just about every driver in the Linux kernel. These are primarily intended to be used for installation, but there’s no real reason that you couldn’t continue to run them after you have installed. The other type of kernel is the generic kernel, in which nearly every driver is built as a module. To use a generic kernel you’ll need to build an initrd to load your filesystem module and possibly your drive controller or other drivers needed at boot time, configure LILO to load the initrd at boot, and reinstall LILO. See the docs in /boot after installing for more information. Slackware’s Linux kernels come in both SMP and non-SMP types now. The SMP kernel supports multiple processors, multi-core CPUs, HyperThreading, and about every other optimization available. In our own testing this kernel has proven to be fast, stable, and reliable. We recommend using the SMP kernel even on single processor machines if it will run on them. Note that on x86_64 (64-bit), all the kernels are SMP capable.
Here are some of the advanced features of Slackware 14.1:
- Runs the 3.10.17 version of the Linux kernel from ftp.kernel.org.
The 3.10.x series is well-tested, offers good performance, and will be
getting long term support from kernel.org. For people interested in
running the previous long term support kernel series, we’ve provided
sample configuration files for Linux 3.4.66 under the /testing directory.
And, to make it easier for people who want to compile the latest Linux
kernel, we’ve also put configuration files for Linux 3.12 in /testing.
- System binaries are linked with the GNU C Library, version 2.17.
This version of glibc also has excellent compatibility with
- X11 based on the X.Org Foundation’s modular X Window System.
This is X11R7.7, a new release, with many improvements in terms of
performance and hardware support.
- Installs gcc-4.8.2 as the default C, C++, Objective-C,
Fortran-77/95/2003/2008, and Ada 95/2005/2012 compiler.
- Also includes LLVM and Clang, an alternate compiler for C, C++,
Objective-C and Objective-C++.
- The x86_64 version of Slackware 14.1 supports installation and booting
on machines using UEFI firmware.
- Support for NetworkManager for simple configuration of wired and
wireless network connections, including mobile broadband, IPv6, VPN,
and more. Roam seamlessly between known networks, and quickly set
up new connections. We’ve retained full support for the traditional
Slackware networking scripts and for the wicd network manager,
offering choice and flexibility to all levels of users.
- Support for fully encrypted network connections with OpenSSL,
OpenSSH, OpenVPN, and GnuPG.
- Apache (httpd) 2.4.6 web server with Dynamic Shared Object
support, SSL, and PHP 5.4.20.
- USB, IEEE 1394 (FireWire), and ACPI support, as well as legacy PCMCIA
and Cardbus support. This makes Slackware a great operating system
for your laptop.
- The udev dynamic device management system for Linux 3.x.
This locates and configures most hardware automatically as it
is added (or removed) from the system, loading kernel modules
as needed. It works along with the kernel’s devtmpfs filesystem
to create access nodes in the /dev directory.
- New development tools, including Perl 5.18.1, Python 2.7.5,
Ruby 1.9.3-p448, Subversion 1.7.13, git-1.8.4, mercurial-2.7.2,
graphical tools like Qt designer and KDevelop, and much more.
- Updated versions of the Slackware package management tools make it
easy to add, remove, upgrade, and make your own Slackware packages.
Package tracking makes it easy to upgrade from Slackware 14.0 to
Slackware 14.1 (see UPGRADE.TXT and CHANGES_AND_HINTS.TXT).
The slackpkg tool can also help update from an older version of
Slackware to a newer one, and keep your Slackware system up to date.
In addition, the slacktrack utility will help you build and maintain
your own packages.
- Web browsers galore! Includes KDE’s Konqueror 4.10.5, SeaMonkey 2.21
(this is the replacement for the Mozilla Suite), Mozilla Firefox ESR 24.1,
as well as the Thunderbird 24.1 email and news client with advanced
junk mail filtering. A script is also available in /extra to repackage
Google Chrome as a native Slackware package.
- The KDE Software Compilation 4.10.5, a complete desktop environment.
This includes the Calligra productivity suite (previously known as
KOffice), networking tools, GUI development with KDevelop, multimedia
tools (including the Amarok music player and K3B disc burning software),
the Konqueror web browser and file manager, dozens of games and utilities,
international language support, and more.
- A collection of GTK+ based applications including pidgin-2.10.7,
gimp-2.8.6 (with many improvements including a single window mode),
gkrellm-2.3.5, xchat-2.8.8, xsane-0.998, and pan-0.139.
- A repository of extra software packages compiled and ready to run
in the /extra directory.
- Many more improved and upgraded packages than we can list here. For
a complete list of core packages in Slackware 14.1, see this file:
Downloading Slackware 14.1:
The full version of Slackware Linux 14.1 is available for download from the central Slackware FTP site hosted by our friends at osuosl.org:
If the sites are busy, see the list of official mirror sites here:
We will be setting up BitTorrent downloads for the official ISO images. Stay tuned to http://slackware.com for the latest updates.
Instructions for burning the Slackware tree onto install discs may be found in the isolinux directory.
Purchasing Slackware on CD-ROM or DVD:
Or, please consider purchasing the Slackware Linux 14.1 six CD-ROM set or deluxe dual-sided DVD release directly from Slackware Linux, and you’ll be helping to support the continued development of Slackware Linux!
The DVD release has the 32-bit x86 Slackware 14.1 release on one side, and the 64-bit x86_64 Slackware 14.1 release on the other. Both sides are bootable for easy installation, and includes everything from both releases of Slackware 14.1, including the complete source code trees.
The 6 CD-ROM release of Slackware 14.1 is the 32-bit x86 edition. It includes a bootable first CD-ROM for easy installation. The 6 CD-ROMs are labeled for easy reference.
The Slackware 14.1 x86 6 CD-ROM set is $49.95 plus shipping, or choose the Slackware 14.1 x86/x86_64 dual-sided DVD (also $49.95 plus shipping).
Slackware Linux is also available by subscription. When we release a new version of Slackware (which is normally once or twice a year) we ship it to you and bill your credit card for a reduced subscription price ($32.99 for the CD-ROM set, or $39.95 for the DVD) plus shipping.
For shipping options, see the Slackware store website. Before ordering express shipping, you may wish to check that we have the product in stock. We make releases to the net at the same time as disc production begins, so there is a lag between the online release and the shipping of media. But, even if you download now you can still buy the official media later. You’ll feel good, be helping the project, and have a great decorative item perfect for any computer room shelf.
You can order online at the Slackware Linux store:
Other Slackware items like t-shirts, caps, pins, and stickers can also be found here. These will help you find and identify yourself to your fellow Slackware users.
Order inquiries (including questions about becoming a Slackware reseller) may be directed to this address: firstname.lastname@example.org
Have fun! :^) I hope you find Slackware to be useful, and thanks
very much for your support of this project over the years.
Patrick J. Volkerding <email@example.com>
Visit us on the web at: http://slackware.com
Thanks to Pat V., the Slackware Linux team, and everyone who has contributed to and supported Slackware throughout the years!
Don’t forget to share your knowledge and gain some knowledge at the Slackware Documentation Project.
Sources: quoted announcement from the Slackware release Announcement.
A few days ago Guillermo Garron wrote a piece on his website after seeing you speak live. A link to that article was posted at Scot’s Newsletter Forums – Bruno’s All Things Linux, where a discussion ensued. During the course of that conversation, I thought that maybe it was about time that we started using a less bulky nomenclature for the GNU/Linux operating system. I posted a few suggestions, but I think I like GNix the best.
A worthy contraction of terms, I think. While I’ve always tried to refer to my favorite operating system as GNU/Linux in my public articles and other posts around the Internet, I often lapse into the shorthand version of “Linux” that is commonly misused by most everyone else in this community; mostly because of the bulkiness of GNU/Linux.
No Windows fans, that I know of, go around calling their operating system Microsoft Windows whatever version. They just call it “Windows”, usually. They know it’s Microsoft. They’re just lazy, as are most of us in the GNU/Linux community of users. So, my thoughts are let’s call it GNix (pronounced g’nicks).
I doubt Linus would mind. He might like it, too. You never know. A marriage of the Linux kernel and the GNU operating system should have a worthy moniker. Maybe now is that time for it to be.
I’m running Slackware GNix as my primary OS on all my machines, but I also have Debian GNix and Fedora GNix installed as testers. Hmm… that rolls off the keypad pretty nicely, I think.
This is a reblog of a hilarious (and true) article from Branko’s Thought Dump.
On the state of Windows on the desktop
I have this Linux system on my PC which has become a bit boring (no, it’s not crashed or anything… I just got a bit bored), so I decided to replace it with Windows 7 (some friends told me to not even try Windows 8 because it has an advanced interface nobody was able to figure out yet).
I really did not set the bar too high: I just hoped to have a nice user-friendly interface and recover the email I have in Maildir, and maybe watch my video collection on an external hard drive. You know, the usual stuff I do on Linux every day.
Please note that this article is a parody of what some Windows users write about Linux. The events described here have not actually taken place. However, the article is based on author’s experiences with the Windows 7 operating system.
I didn’t want to commit and install a new operating system right off the bat. I just wanted to try it first. So I typed “Windows Live” in my browser’s search box to find a live version, preferably an USB image. Ok, so Windows Live wasn’t a live version of windows but some kind of service you must sign into. I guess it’s something like Ubuntu One. Not sure. Moreover, it turned out I’d have to actually buy it first before I could do anything with it. And there is not real live version of Windows 7.
Read the rest of this entertaining article HERE.
*Special thanks to pal SecurityBreach/Comhack for posting this at Scot’s Newsletter Forums this morning. It will be my Laugh of the Day for today, for sure!
P.S. Certification studies going well.
Earlier today, I received an email from Jeremy @ LinuxQuestions.org alerting me to his recent interview of Pat V.
It is absolutely outstanding. I enjoyed it very much. You should give it a looksee…
My niece deposited her old, tired Dell Latitude D560 laptop on her old, tired uncle yesterday.
She knew that he would wipe that ol’ corrupted Win XP installation off that baby and make ‘er scream again with a nice efficient GNU/Linux operating system. With a 30Gig hdd and only 760M of RAM, screaming will be only moderate with his little machine. However, scream again she does with a fresh install of Vector Linux 7.0 Standard (32 bit).
I had fully intended to give newcomer to the GNU/Linux scene, Zorin, a go on this old lappy. Unfortunately, their download hosting sites were terribly slow today; I mean dial-up slow. The NLUUG Netherlands site was faster than the U.S. iBiblio site, but that ain’t saying much. Either one was stating 11-12 hours download time for a measly 1.1Gig .iso file. That’s just sad. Oh well, maybe another time for Zorin. It does look promising; particularly as a transitional OS from Win to Lin.
Today, though, Vector won out in the download speed race. I’ve used Vector off and on across numerous of my systems and platforms over the past 6 or 7 years. It has always been a stable, usable, no-surprises distribution. I like that. I’m not a fan of surprises when it comes to operating systems. I like boring. I’ve been reluctant, as mentioned elsewhere here, to install Vector on my main or shop systems because I’m patiently waiting for a 64 bit version. A 32 bit version was just what this lappy needed; one not too bloated.
Installation was almost Slackware-ish boring. As I said, no surprises… GOOD! I installed on ext3 partitions; one for / and one for /home, as is my standard practice with GNU/Linux. The entire installation took about 15 minutes or so. I’m running the default Xfce/Cairo Dock desktop at the moment. It’s pretty nice, actually. Ethernet and wireless work out-of-the-box; again, no surprises.
Here’s a pic of the peppy and refreshed old laptop (click of bigger pic):
So, there you have it. Have an old, tired laptop lying around out in the garage? Grab it and install a fresh Vector Linux install on that baby and off you’ll go. That lappy will be a fully-functional machine once again. Set it up for the kids. Donate it to some needy person. Whatever you do with it will be better than what it was doing, sitting on that shelf all lonely and neglected.
So, most of you GNU/Linux users have by now peaked into that File System directory on the left frame of your file manager, huh?
It seems that back in the day (early 70s), when Ken Thompson and Dennis Ritchie were at Bell Labs tinkering around with Unix in its infancy, how they came to name these directories was primarily determined by their available storage space at the time. Geeks just being practical; ain’t it great?
From busybox.net list:
Thu Dec 9 15:45:39 UTC 2010
When the operating system grew too big to fit on the first RK05 disk pack (their root filesystem) they let it leak into the second one, which is where all the user home directories lived (which is why the mount was called /usr). They replicated all the OS directories under there (/bin, /sbin, /lib, /tmp…) and wrote files to those new directories because their original disk was out of space. When they got a third disk, they mounted it on /home and relocated all the user directories to there so the OS could consume all the space on both disks and grow to THREE WHOLE MEGABYTES (ooooh!).
3Meg… WOW! Nowadays, we dash off inane missives that often exceed 3 Meg in size. We don’t even think about it. Can you imagine? I was 10 years old in ’71, running around in a neighbor’s overgrown yard playing “war” with my pals. Dennis and Ken were in their late twenties and using their genius to create the foundation for pretty much everything you see in front of you right now… the Internet, the operating system on your computer, the code that is the foundation for most of it, etc. Amazing, huh?
Thom Holwerda from his OSNews article laments:
Arguing that the UNIX directory structure is a horrible, horrible mess that defiles an otherwise elegant system is like trying to convince a floor tile to flip over. People are so used to their knee-jerk responses about how it all supposedly makes sense, they often refuse to even think about redesigning it for the modern age. Since the geek is a proud and stubborn creature, there’s little to no chance of this ever changing in my lifetime.
Thom is not a big fan of the Unix file structure. I can see his points. When you read how those directories actually came about, you begin to wonder, as Thom often does, whether the whole thing needs a reboot/rename. Well, it probably won’t ever happen. Hell, some of us still like to boot into a command line interface rather than a graphic one. Holwerda says that geeks are a proud and stubborn. Yup… mostly stubborn.
Read the article. Click on the links. It’s some interesting stuff, folks.