Language Selection

English French German Italian Portuguese Spanish

Slackware 10.2

Filed under
Reviews
Slack
-s

It's no secret that Slackware 10.2 was released yesterday. This was big news and headlined many sites as well as being announced on DistroWatch with the links to download torrents. Slackware puts out a new release once or maybe twice a year if the community is lucky, so when they do release a new version, it's big news. I, like many of you, have been on pins and needles for several weeks now since hints of a impending new release leaked out. Then anticipation grew when the changelog of last week made the press announcing 10.2 was almost ready and should be out probably by Tuesday. Torrents were made public yesterday and I grabbed my place in line. Excitement overwhelmed me as I booted the install disk. I was not disappointed in what I found.

The announcement included such goodies as Support for fully encrypted network connections with OpenSSL, OpenSSH, and GnuPG; New development tools, including Perl 5.8.7, Python 2.4.1, Subversion 1.2.3, and graphical tools like Qt designer and KDevelop; and an Updated versions of the Slackware package management tools make it easy to add, remove, upgrade, and make your own Slackware packages.

The most exciting news to me in the announcement was the availability of the 2.6.13 kernel. Slackware installs the 2.4.31 kernel as default and functions very well at that. However, if one mounts the 2nd install cdrom, they can install the 2.6.13 kernel using installpkg.


mount -t auto /dev/hd<x> /mnt/cdrom


where the cdrom is the 2nd install disk. Then simply issue the following command:

installpkg /mnt/cdrom/linux-2.6.13/kernel-source-2.6.13-noarch-1.tgz /mnt/cdrom/linux-2.6.13/kernel-modules-2.6.13-i486-1.tgz /mnt/cdrom/linux-2.6.13/kernel-headers-2.6.13-i386-1.tgz /mnt/cdrom/linux-2.6.13/kernel-generic-2.6.13-i486-1.tgz
/mnt/cdrom/linux-2.6.13/alsa-driver-1.0.9b_2.6.13-i486.1.tgz

Then you are going to need to make an initrd image as well if you installed onto any kind of filesystem other than ext2, unless you'd rather rebuild the kernel. In this case I chose to install mkinitrd and make the initrd image. So mount the first install disk and:

installpkg /mnt/cdrom/slackware/a/mkinitrd-1.0.1-i486-3.tgz

Next you need to make your initrd image. For example:

mkinitrd -c -k 2.6.13 -m reiserfs

Then put an entry in /etc/lilo.conf (or grub files), run lilo, and reboot. For example, my lilo entry looks like this:


image=/boot/vmlinuz-generic-2.6.13
label="slack-10.2"
root=/dev/hda17
initrd=/boot/initrd-generic-2.6.13.img
append="resume=/dev/hda7"
vga=791
read-only

After boot you get all of slack's goodness. This go around they have included xfce4 as well as some of the other popular window managers such as Fluxbox and Blackbox. Included versions are xfce4-4.2.2, windowmaker 0.92.0 and kde 3.4.2.

    

    

In the past I enjoyed Slackware for it's ease of configuration, all set up nice and easy in a few start up files. But these days, one really doesn't have to mess with that too much. I personally didn't have to change a thing. All my hardware was detected properly and functioned perfectly upon boot.

The changelog is chocked full of version upgrades and bug fixes, but also some new additions as well. Some of highlights include:

  • d/subversion-1.2.3-i486-1.tgz: Added subversion-1.2.3.

  • l/jre-1_5_0_04-i586-2.tgz: Added /usr/lib/mozilla/plugins directory with a link to the Java plugin.
  • ap/vorbis-tools-1.1.1-i486-1.tgz: Upgraded to vorbis-tools-1.1.1.
  • kde/kdebase-3.4.2-i486-2.tgz: Patched a bug in Konqueror
  • kde/kdebase-3.4.2-i486-1.tgz: Upgraded to KDE 3.4.2.
  • extra/bash-completion/bash-completion-20050721-noarch-1.tgz:
    Upgraded to bash-completion-20050721.

  • testing/packages/php-5.0.5/php-5.0.5-i486-4.tgz:
    Upgraded to php-5.0.5

  • testing/packages/linux-2.6.13/kernel-source-2.6.13-noarch-1.tgz:
    Upgraded to Linux 2.6.13

  • ap/mysql-4.1.14-i486-1.tgz: Upgraded to mysql-4.1.14.
  • d/gcc-3.3.6-i486-1.tgz: Upgraded to gcc-3.3.6.
  • x/x11-6.8.2-i486-1.tgz: Upgraded to X11R6.8.2.
  • Full Changelog HERE

So, there were some exciting changes and yet it was still the same reliable stable Slackware. If you've never tried Slackware, there isn't a better time than the present.

Correction

Just a quick correction...

installpkg /mnt/cdrom/kernel-2.6.13/kernel-source-2.6.13-noarch-1.tgz /mnt/cdrom/kernel-2.6.13/kernel-modules-2.6.13-i486-1.tgz /mnt/cdrom/kernel-2.6.13/kernel-headers-2.6.13-i386-1.tgz /mnt/cdrom/kernel-2.6.13/kernel-generic-2.6.13-i486-1.tgz
/mnt/cdrom/kernel-2.6.13/alsa-driver-1.0.9b_2.6.13-i486.1.tgz

Should be

installpkg /mnt/cdrom/linux-2.6.13/kernel-source-2.6.13-noarch-1.tgz /mnt/cdrom/linux-2.6.13/kernel-modules-2.6.13-i486-1.tgz /mnt/cdrom/linux-2.6.13/kernel-headers-2.6.13-i386-1.tgz /mnt/cdrom/linux-2.6.13/kernel-generic-2.6.13-i486-1.tgz
/mnt/cdrom/linux-2.6.13/alsa-driver-1.0.9b_2.6.13-i486.1.tgz

Insert_Ending_Here

re: Correction

ohhh, ok, I finally see the difference. lol... I looked at your post many times and just could not see it. Blushing

Thanks! Smile

----
You talk the talk, but do you waddle the waddle?

Another correction...

image=/boot/vmlinuz-generic-2.6.13
label="slack-10.2"
root=/dev/hda17
initrd=/boot/initrd-generic-2.6.13.img
append="resume=/dev/hda7"
vga=791
read-only

Should be:

image=/boot/vmlinuz-generic-2.6.13
label="slack-10.2"
root=/dev/hda17
initrd=/boot/initrd.gz
append="resume=/dev/hda7"
vga=791
read-only

Insert_Ending_Here

re: vga=791

yeah, it's a real nice "resolution" for the terminal on a 17" monitor. Booting looks nice at that setting as well, but I use it mainly cuz it' makes the terminal so much more useful for me. ...amounts to more screen real estate and the fonts look nicer too. Thanks for saying. Smile

----
You talk the talk, but do you waddle the waddle?

re: initrd

as far as the initrd-generic-2.6.13.img, it's what I named mine cuz as you might imagine, my boot partition is overflowing with files - I have to name things kinda distinctively - if they aren't already.

----
You talk the talk, but do you waddle the waddle?

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

[CentOS-announce] Release for CentOS Linux 7 (1908) on the x86_64 Architecture

Release for CentOS Linux 7 (1908) on the x86_64 Architecture We are pleased to announce the general availability of CentOS Linux 7 (1908) for the x86_64 architecture. Effectively immediately, this is the current release for CentOS Linux 7 and is tagged as 1908, derived from Red Hat Enterprise Linux 7.7 Source Code. As always, read through the Release Notes at : http://wiki.centos.org/Manuals/ReleaseNotes/CentOS7 - these notes contain important information about the release and details about some of the content inside the release from the CentOS QA team. These notes are updated constantly to include issues and incorporate feedback from the users. Read more Also: CentOS 7.7 Released As The Last Stop Before CentOS 8.0

The 32-Bit Packages That Will Continue To Be Supported Through Ubuntu 20.04 LTS

Earlier this year Canonical announced they would be pulling 32-bit support from Ubuntu ahead of next year's 20.04 LTS. But following public backlash, they stepped back to provide 32-bit support for select packages. Today they announced the 199 32-bit packages that will continue to be supported through Ubuntu 20.04 LTS. Based upon popularity when looking at i386 packages that are not x86_64 (AMD64) packaged as well as feedback from their customers/partners, they have come up with a list of the 32-bit packages they will continue to support. Their list is 52 packages but with dependencies comes out to about 199 packages in the i386 realm they will continue to support. Read more Also: Ubuntu Devs Detail Plan for 32-bit Support in Ubuntu 19.10

AMD EPYC 7302 / 7402 / 7502 / 7742 Linux Performance Benchmarks

Last month we provided launch-day benchmarks of the AMD EPYC 7502 and 7742 under Linux in both 1P and 2P configurations for these exciting "Rome" Zen 2 server processors. For your viewing pleasure today is a fresh look at not only the EPYC 7502 and 7742 processors under the latest Linux 5.3 kernel but we've also expanded it to looking at the EPYC 7302 and EPYC 7402 processors as well with those processors recently being sent over by AMD. Under Ubuntu 19.04 with Linux 5.3, these four different AMD EPYC 7002 series SKUs were benchmarked along with some of the older AMD Naples processors and Intel Xeon Gold/Platinum processors for a fresh look at the Linux server performance. Read more

Mozilla: Media and Truth, Security and More

  • Examining AI’s Effect on Media and Truth

    Today, one of the biggest issues facing the internet — and society — is misinformation. It’s a complicated issue, but this much is certain: The artificial intelligence (AI) powering the internet is complicit. Platforms like YouTube and Facebook recommend and amplify content that will keep us clicking, even if it’s radical or flat out wrong. Earlier this year, Mozilla called for art and advocacy projects that illuminate the role AI plays in spreading misinformation. And today, we’re announcing the winners: Eight projects that highlight how AI like machine learning impacts our understanding of the truth.

  • Mozilla Open Policy & Advocacy Blog: Governments should work to strengthen online security, not undermine it

    On Friday, Mozilla filed comments in a case brought by Privacy International in the European Court of Human Rights involving government “computer network exploitation” (“CNE”)—or, as it is more colloquially known, government hacking. While the case focuses on the direct privacy and freedom of expression implications of UK government hacking, Mozilla intervened in order to showcase the further, downstream risks to users and internet security inherent in state CNE. Our submission highlights the security and related privacy threats from government stockpiling and use of technology vulnerabilities and exploits. Government CNE relies on the secret discovery or introduction of vulnerabilities—i.e., bugs in software, computers, networks, or other systems that create security weaknesses. “Exploits” are then built on top of the vulnerabilities. These exploits are essentially tools that take advantage of vulnerabilities in order to overcome the security of the software, hardware, or system for purposes of information gathering or disruption. When such vulnerabilities are kept secret, they can’t be patched by companies, and the products containing the vulnerabilities continue to be distributed, leaving people at risk. The problem arises because no one—including government—can perfectly secure information about a vulnerability. Vulnerabilities can be and are independently discovered by third parties and inadvertently leaked or stolen from government.

  • Time for some project updates

    I’m going to begin with some of the less-loved things I’ve been working on, partially in an attempt to motivate some forward-motion on things that I believe are rather important to Mozilla.