From d6deb72ed42a0d145f5fc6f825d5b0ae090baafd Mon Sep 17 00:00:00 2001 From: Klaatu Date: Fri, 22 Jun 2012 23:37:52 -0400 Subject: Added and corrected docbook markup. Added content to the very sparse section on slackpkg Added a section about rpm2tgz in the package management section Added some obvious indexterms and xref ids --- chapter_18.xml | 122 ++++++++++++++++++++++++++++++++++----------------------- 1 file changed, 73 insertions(+), 49 deletions(-) (limited to 'chapter_18.xml') diff --git a/chapter_18.xml b/chapter_18.xml index ea3035c..458b28f 100644 --- a/chapter_18.xml +++ b/chapter_18.xml @@ -2,59 +2,69 @@ - + Keeping Track of Updates -
+ + system updates + + +
The -stable Branch -Whenever a new version of Slackware is released, the Slackware team will, -as needed, release updated packages to fix serious security vulnerabilities -and particularly nasty bugs. Therefore, it's important to keep up with all -of the patches for your version of Slackware, which is referred to as the -"-stable" branch. There is also a "-current" branch, which is where we do -our development work toward the next stable release (and as such, there are -often intrusive changes there), but unless you're willing to work with a -possibly broken system and are able to fix things on your own, we strongly -recommend that you stick with the "-stable" branch. +After a new version of Slackware is released, the Slackware team will, +as needed, release updated packages to fix serious security +vulnerabilities and particularly nasty bugs. Therefore, it's +important to keep up with all of the patches for your version of +Slackware, which is referred to as the -stable +branch. There is also a -current branch, which +is where we do our development work toward the next stable release +(and as such, there are often intrusive changes there), but unless +you're willing to work with a possibly broken system and are able to +fix things on your own, we strongly recommend that you stick with the +-stable branch. -Since -stable updates aren't distributed on the disks, you'll need to obtain -them from the Internet. Many people and organizations offer mirrors from -which you can download the entire Slackware tree (or only the -patches/ directory) in any number of ways. While some -mirrors offer web access, the most common ways of obtaining updates are via -ftp and/or rsync servers. The Slackware project maintains a small list -(organized by country) of known mirrors. If you're unsure which mirror you -should use, simply consult -http://www.slackware.com/getslack/ -for suggestions. If you have a major university near you, there's a good -chance that they offer a mirror of numerous open source projects, and -Slackware may be among them. The only real requirement for a mirror is that -it be complete, but usually it's best to use a mirror near where you live in -order to achieve the fastest transfer times and use the least amount of -Internet resources. +Since -stable updates aren't distributed on the disks, you'll need to +obtain them from the Internet. Many people and organizations offer +mirrors from which you can download the entire Slackware tree (or only +the patches/ directory) in any number of +ways. While some mirrors offer web access, the most common ways of +obtaining updates are via ftp and/or rsync servers. The Slackware +project maintains a small list (organized by country) of known +mirrors. If you're unsure which mirror to use, simply consult http://www.slackware.com/getslack/ +for suggestions. If you have a major university near you, there's a +good chance that they offer a mirror of numerous open source projects, +and Slackware may be among them. The only real requirement for a +mirror is that it be complete; usually it's best to use a mirror near +where you live in order to achieve the fastest transfer times and use +the least amount of Internet resources. + + changelog + + So how do you know when there are updates? The best way is to consult the ChangeLog.txt on any up-to-date mirror. You can always -find the latest changelogs for the "-current" and most recent "-stable" +find the latest changelogs for the -current and most recent -stable branch on the Slackware Project's web page, but if you're running an older version of Slackware, you'll need to check a mirror. -darkstar:~# wget -O - \ -ftp://slackware.osuosl.org/pub/slackware/slackware-13.0/ChangeLog.txt \ +darkstar:~# wget -O - \ +ftp://slackware.osuosl.org/pub/slackware/slackware-13.0/ChangeLog.txt \ | less Sun Jan 24 20:22:46 UTC 2010 -patches/packages/httpd-2.2.14-i486-1_slack12.1.tgz: Upgraded. +patches/packages/httpd-2.2.14-i486-1_slack12.1.tgz: Upgraded. This fixes a couple of security bugs when using mod_proxy_ftp. For more information, see: - http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-3094 - http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-3095 + http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-3094 + http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-3095 (* Security fix *)
@@ -76,9 +86,16 @@ packages are released, it will mail an advisory to you.
-
+
Upgrading Slackware Versions + + system upgrade + + + operating system upgrade + + Now that we've gone this far, you should feel reasonably competent in your ability to manage your Slackware system. But what do we do with it when @@ -95,20 +112,28 @@ you, Slackware takes a much more hands-on approach to things. The very first thing you should do before attempting an upgrade is the one that many people neglect: decide if it's really necessary to upgrade. If the old system is stable and doing everything you want it to do, there may -be no need to do an operating system upgrade at all. Assuming you decide -to do the upgrade, then the second thing you should do is read the -CHANGES_AND_HINTS.TXT file on your upgrade discs or -a mirror. This file is updated during the development period before every -release, and it lists lots of helpful hints and tips to aid you in dealing -with the changes. Finally, read the UPGRADE.TXT file -before proceeding. After doing these things, you may decide that it's less -trouble and potential for problems to backup your configuration files and -data and do a fresh installation of the new Slackware release rather than -attempt a possibly tricky upgrade. However, if you still wish to continue, -make backups of your data and configuration files first. At a minimum, -it's good practice to backup the /etc and /home -directories. This will give you a chance to perform a reinstall if something -goes wrong with the upgrade. +be no need to do an operating system upgrade at all. + + + +Assuming you decide to do the upgrade, then the second thing you +should do is read the CHANGES_AND_HINTS.TXT file +on your upgrade discs or a mirror. This file is updated during the +development period before every release, and it lists a lot of helpful +hints and tips to aid you in dealing with the changes. + + + +Finally, read the UPGRADE.TXT file before +proceeding. After doing these things, you may decide that it's less +trouble and potential for problems to backup your configuration files +and data and do a fresh installation of the new Slackware release +rather than attempt a possibly tricky upgrade. However, if you still +wish to continue, make backups of your data and configuration files +first. At a minimum, it's good practice to backup the +/etc and /home directories. +This will give you a chance to perform a reinstall if something goes +wrong with the upgrade. @@ -119,5 +144,4 @@ favorite mirror.
- - + \ No newline at end of file -- cgit v1.2.3