[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
slackbook:tracking_updates [2012/09/17 03:17 (UTC)] – [The -stable Branch] Added original text and formatting mfillpot | slackbook:tracking_updates [2012/09/17 03:21 (UTC)] (current) – [Sources] updated author list mfillpot | ||
---|---|---|---|
Line 56: | Line 56: | ||
===== Security Update Mailing List ===== | ===== Security Update Mailing List ===== | ||
- | While the Slackware team does release updated bugfix-only packages (i.e. not security fixes) occasionally, | + | While the Slackware team does release updated bugfix-only packages (i.e. |
+ | not security fixes) occasionally, | ||
+ | security fixes for vulnerabilities discovered after the -stable release. | ||
+ | The Slackware Project maintains a mailing list that will notify you of any | ||
+ | updated packages for such serious issues. | ||
+ | mailing list, send an e-mail to < | ||
+ | with the words **subscribe slackware-security** in the body of the message. | ||
+ | The majordomo will be happy to add your name to the list, and when new | ||
+ | packages are released, it will mail an advisory to you. | ||
===== Upgrading Slackware Versions ===== | ===== Upgrading Slackware Versions ===== | ||
- | 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 there' | + | Now that we've gone this far, you should feel reasonably competent in your |
+ | ability to manage your Slackware system. | ||
+ | there' | ||
+ | is a lot more complicated than simply updating a few packages. | ||
+ | changes a lot of things, and while many of these changes are small, some of | ||
+ | them can completely break your system if you haven' | ||
+ | don't understand what is changing and why. While some Linux distributions | ||
+ | provide highly automated tools that attempt to handle every tiny detail for | ||
+ | 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. | ||
+ | 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. | ||
- | The very first thing you should do before attempting an upgrade | + | Assuming you decide to do the upgrade, then the second |
+ | should do is read the '' | ||
+ | on your upgrade | ||
+ | development period before every release, | ||
+ | hints and tips to aid you in dealing with the changes. | ||
- | 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. | + | Finally, read the '' |
+ | proceeding. | ||
+ | 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. | ||
+ | wish to continue, make backups of your data and configuration files | ||
+ | first. | ||
+ | '' | ||
+ | This will give you a chance to perform a reinstall if something goes | ||
+ | wrong with the upgrade. | ||
- | Since every new version of Slackware has a few differences, | ||
+ | Since every new version of Slackware has a few differences, | ||
+ | instructions here is not only futile but potentially misleading. | ||
+ | always consult the documentation included on your Slackware disks or your | ||
+ | favorite mirror. | ||
====== Chapter Navigation ====== | ====== Chapter Navigation ====== | ||
Line 78: | Line 115: | ||
====== Sources ====== | ====== Sources ====== | ||
<!-- If you copy information from another source, then specify that source --> | <!-- If you copy information from another source, then specify that source --> | ||
- | * Original source: [[http:// | + | * Original source: [[http:// |
<!-- Authors are allowed to give credit to themselves! --> | <!-- Authors are allowed to give credit to themselves! --> | ||
- | * Originally written by Alan Hicks | + | * Originally written by Alan Hicks, Chris Lumens, David Cantrell, Logan Johnson |
<!-- * Contrbutions by [[wiki: | <!-- * Contrbutions by [[wiki: | ||