Language Selection

English French German Italian Portuguese Spanish

Slackware 10.2

Submitted by srlinuxx on Friday 16th of September 2005 01:41:24 AM 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

Submitted by Devnet on Saturday 17th of September 2005 02:26:07 AM.

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

Submitted by srlinuxx on Monday 19th of September 2005 01:36:16 AM.

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

Submitted by Devnet on Saturday 17th of September 2005 02:40:16 AM.

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

Submitted by srlinuxx on Monday 19th of September 2005 12:38:03 AM.

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

Submitted by srlinuxx on Monday 19th of September 2005 12:50:38 AM.

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

Games: Police Stories, Total War: WARHAMMER II and GOG

  • Some thoughts on Police Stories, the recently released slower tactical top-down shooter

    Released earlier this month, Police Stories attempts to slow down the top-down shooter genre with a more tactical approach and most of the time it works quite well. The story here revolves around two cops, John Rimes and Rick Jones. Two old friends joined together as partners when you move to the city. Starting off from a simple call to action while on duty, things quickly spiral as you uncover links leading to something much bigger than expected.

  • Total War: WARHAMMER II - The Hunter & The Beast is now on Linux, plus The Empire Undivided update

    Feral Interactive have updated their port of Total War: WARHAMMER II for Linux to bring The Empire Undivided update and The Hunter & The Beast DLC is now supported. The Empire Undivided free content update is huge, so big it has a long dedicated post to it on the Total War blog. There's masses of bug fixes and overall balance improvements but also some huge feature adjustments too. The biggest changes looks like it happened for the Mortal Empires Campaign, which is what you get free if you own both Total War: WARHAMMER and Total War: WARHAMMER II. A big territory rework with 12 new regions, huge forts to battle through and empire factions now have access to the reworked Empire tech tree. The Empire Offices system was thrown out too, replaced with a new authority system. There's a huge amount more to it, so do take a read if you're interested in the full details.

  • DUSK with an exclusive map and Chasm come to GOG during their big 11th anniversary celebration

    GOG has been going for just about 11 years now, so they're having a big sale to celebrate. On top of that the retro FPS DUSK is now on GOG with an exclusive GOGATORIUM map for the endless mode and also CHASM is now on GOG too.

Solus 4 Users Are Among the First to Use the GNOME 3.34 Desktop Environment

The Solus Project announced today that the latest GNOME 3.34 desktop environment is now available for all users of the independently developed Linux-based computer operating system, along with many other updates and bug fixes. Launched in mid-September, the GNOME 3.34 desktop environment has only been available for a few GNU/Linux distributions as upgrading from a previous release looks to be a rigorous and hard process for OS vendors. Solus 4 users are now among the first to use GNOME 3.34 on their personal computers. "This stack upgrade has been rigorously tested by a wide range of users via our unstable repository, all of whom provided valuable feedback and reports over on our development tracker. This upgrade has also fortunately been smoother compared to previous stack upgrades," said lead developer Joshua Strobl in the latest news roundup. Read more

Programming: PyCharm, Qt and More

  • 2019.3 EAP 4

    This week’s Early Access Program (EAP) for PyCharm 2019.3 is available now! Download it from our website.

  • Bring in the WhiteNoise, Bring in Da Funk - Building SaaS #34

    In this episode, we added WhiteNoise to the app as a tool for handling static assets. This lets us move away from depending on Nginx for the task and gives shiny new features like Brotli support.

  • A fast and thread-safe pool allocator for Qt - Part 2

    In part 1 of this blog series, we developed a pool allocator that is optimized for small allocations. We confirmed that we do that a lot in Qt when we allocate QEvent or QObject instances, and a specialized allocator might be useful for application developers as well. So far, our solutions will allocate complete pages of memory as needed, and hand out memory chunks of a fixed size that is specified at compile time through a template parameter. It supports different threading models, with different tradeoffs regarding performance, memory efficiency, and concurrency. The results were giving us a very promising performance, beating the general-purpose allocators by a factor of 3-10 in our multi-threaded benchmarks. However, with an allocator that can only handle one chunk-size, and never returns memory back to the operating system, we still have a way to go before we can really support our QEvent and QObject use cases within Qt. We can't just make our library waste and hog memory, or require application developers to reimplement operator new/delete to be able to allocate instances of their larger subclasses!

  • KDE & Qt Applications and High DPI Displays with Scaling

    In the past, most displays had (or the OS pretended to have) around 96 PPI, more or less. If you differed a bit and had too small/large UI elements, you mostly just resized your default font size a bit and were kind of happy. In the last years, more and more displays arise that have a much higher PPI values, which allows for e.g. very crisp rendering of text. I arrived late in that era for my Linux machines by now starting to use two 163 PPI displays. Just tweaking your fonts doesn’t help here, all other things will still be unbearable small, even if you in addition increase e.g. icon sizes. A solution for this is the current trend to just “scale” your UI by some factor, for my displays some factor of 1.5 leads to the most pleasant sizes.

  • dup2 System Call in C

    The dup2() system function is used to create a copy of an existing file descriptor. In Linux, there are 3 standard file descriptors. They are: stdin: This is the standard input file descriptor. It is used to take input from the terminal by default. scanf(), getc() etc functions uses stdin file descriptor to take user inputs. The stdin file descriptor is also represented by the number 0. stdout: This is the standard output file descriptor. It is used to print something to the console/terminal by default. The widely used printf() function uses stdout to print your desired output to the console/terminal. The stdout file descriptor is also represented by the number 1. stderr: This is the standard error file descriptor. It does the same thing as the stdout file descriptor. The stderr file descriptor is used to print error messages on the console/terminal. The only difference is if you use stderr file descriptor to print the error messages, and stdout file descriptor to print normal outputs, then you can later separate them. For example, you can redirect the error messages to a file and normal outputs to the console or another file. The stderr file descriptor is also represented by the number 2.

today's howtos

More on Tux Machines: About ● Gallery ● Forum ● Blogs ● Search ● News ● RSS Feed

Part of Bytes Media ● Sister sites below.

TechBytes Techrights button

Powered by Drupal, an open source content management system

Content available under CC-BY-SA CC

© by original authors

Powered by CentOS 6.5 (GNU/Linux), Varnish, and Drupal 6