#SLACKWARE INSTALLPKG UPGRADE UPDATE#
#SLACKWARE INSTALLPKG UPGRADE UPGRADE#
#SLACKWARE INSTALLPKG UPGRADE DOWNLOAD#

#SLACKWARE INSTALLPKG UPGRADE UPGRADE#

Anyway, every time you upgrade your kernel, you'll need to make sure the paths in /etc/nf point to a valid kernel, and then run /sbin/lilo to reinstall LILO. The default configuration of slapt-get will ignore kernel upgrades, so the only way you'll know about those is by reading the official ChangeLog.

The only exception of which I can think is kernel upgrades thankfully, those haven't happened *too* often in official releases in recent memory, but they do occur frequently enough to be worth considering. While I'm not the author of slapt-get (Jason, feel free to jump in here), it seems to me that this was the original intent of slapt-get (and it works *extremely* well for that task, might I add). If your only goal is to stay up-to-date with official security and stability patches for your version of Slackware, then the default configuration of slapt-get should work fine for you. Usage Hint #1: Security and Stability Patches See the Slackware site ] to find an official mirror site.

Rather than using the official ChangeLog (and bandwidth), it's better to use one of the official Slackware mirrors (you'll notice faster connections with the mirrors): Replace the '12.2' with the release version you're using. UPGRADE.TXT and ChangeLog.txt is still required reading, the latter is especially true when running -current.Д«y the way, don't even consider trying to follow the Slackware -current development using slapt-get that's just *asking* for a problem (for reasons which will hopefully be clear later). You'll be okay most of the time if you ignore this advice, but don't come crying to #slackware if you do.В :) The biggest piece of advice I can give to *anyone* regardless of how/why you're using slapt-get is this: READ THE CHANGELOG! The pertinent portions of the changelog are also viewable for each package using -show option. An individual wishing to upgrade from one release of Slackware to another will have more issues with which to contend than another individual who simply wants to keep up-to-date with official security/stability patches. # for example source entries and configuration hints.Д®XCLUDE=^kernel-.*,^alsa-.*,^glibc.*.*-dl$,^devs$,^udev$,aaa_elflibs,x86_64Дepending upon your individual goals of using slapt-get, the usage hints will vary. # See /usr/doc/slapt-get-0.10.1/example.slapt-getrc

Once it's installed, configure it to point to your favourite Get the slapt-get package for your version of Slackware. As such, any inherent 'limitations' (yes, I use that term loosely) in the pkgtool suite will also apply to slapt-get. Prior to using slapt-get, you should really be familiar with proper usage of the native Slackware package management tools:ДЄs indicated in the link above, slapt-get is *not* a replacement for those utilities - it *uses* those utilities. See the Slapt-get page for an introduction to slapt-get and its functionality. 3.3 Usage Hint #3: Keep Up With Slackware -current Development.3.2.6 Step 6: Go back to multi-user mode.

#SLACKWARE INSTALLPKG UPGRADE UPDATE#

3.2.5 Step 5: Update LILO and config files.3.2.3 Step 3: Put your machine in single-user mode.

#SLACKWARE INSTALLPKG UPGRADE DOWNLOAD#

3.2.2 Step 2: Download all updated packages.

3.2.1 Step 1: Edit your /etc/slapt-get/slaptgetrc.

3.2 Usage Hint #2: Upgrade From One Release To Another.

3.1 Usage Hint #1: Security and Stability Patches.

Slackware installpkg upgrade