Slackware 10.2
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.


Stable slackware?
Slackware has retrograded with 10.2 which has safeharbor of 2.4.31 linux kernel. Avoiding Gnome and 2.6.12 has its merits. Its better stable(Debian popularity) than testing(Ubuntu, Fedora and Mandriva for bug reports) to help the distro to sells their 4 disk setup for $40. Patrick the slackware emperor has spoken.
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.
Thanks!
----
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
Slackware 10.2 overview?
Slackware 10.2 will continue to have updates of many many fixes because of legacy backward compatibilty problems; stable version is only a fixation in my mind with 2.4.31. Fortunately, package addition of 2.6.13 installation helps in udev /usr drivers. But the addition of unionfs and squashfs is still very much a problem for most distros, to complete the enterprise system distributed data transfer schema(what with blades and grids) into dram centric ramdisks. The necessity of using IP address to pull down partitions, directory and file names, then automatically installed into or transferred from ramdisk using search engine; has not been imagined yet, let alone visualized. So, we expect that it will take 6 more months to have bug free 2.6.x(x=22-31 perhaps?) kernels. Footnote: RedHat developer(Westford, Ma.) expected 2 years to put RedHat into compliance with 2.6.x kernels when 2.6 was released; the very reason that fedora started with a new slate. PS. I love your use of vga791, bypassing svga drivers and still have high resolution and as many colors. You can use a minimal video card and still have power.
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.
----
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?
I think you can install with 2.6.13
I installed Slackware current a few days before it went final, and one of the available installation kernels was 2.6.13, listed as test26, IIRC. So you can run the install on 2.6.13 and install it when you're done without all that other stuff. Of course, you have install the modules and so forth by hand later.
As I say, that was Slack current. Maybe he took it out for 10.2 final, but you might want to fire up the installer and see. Then you would be the first place it'd be online, as far as I can tell.
Cheers,
Joe Ferrare
Almost all linux kernels now include 2.6.x package?
If you use 2.6.14(only 3 mb length package including the latest x86-64 patches), you will notice changes in hotplug of USB devices, and installation of other ambiguous(DSP) device drivers in /usr rather than /dev. But you may find some bugs yet; staying with 2.4.31 of course, limits you to older computers. I like 2.6.x on hdd-less fast livecd(s), not as much in Linux hard disk operating system, which has the slow virtual memory or swap file in the hard disk instead of ramdisk. Using livecd, the hdd is used as a pure storage device(could be removable fast USB 480mbps 1.6 terabyte hdd), you have to use unionfs or squashfs to access it and transfer into ramdisk operating system where swap file is another fast ramdisk.
Slackware 11.0 can be bought for its quality ?
Slackware has version 11.0 up for delivery? Half the price of a windows operating system.
What you can expect is the traditional Slackware philosophy. Linux 2.4.32 for the older computers. And testing addition of Linux 2.6.15.6 for hotplug, udev(ndiswrapper) drivers for the latest computers. We don't know if event handling is a key feature or not? Nor do we know if Patrick had coupled unionfs to Mysql for distributed network system event handling synchronization?
But, its exciting to learn that more stable distro is available from Slackware for the latest computers as well.
Footnote:
Microsoft uses autoupdate(on demand) to synchronize all their installed base. Linux open source namely Knopper attempted a file system without going thru file manager to authorize choices. Now we have to rein unionfs back into file manager and file update synchronization(cron jobs on demand) to make Linux 2.6.x perfect.