[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.
Различия
Показаны различия между двумя версиями страницы.
Предыдущая версия справа и слеваПредыдущая версияСледующая версия | Предыдущая версияСледующая версияСледующая версия справа и слева | ||
ru:slackbook:tracking_updates [2013/11/13 09:37 (UTC)] – [Keeping Track of Updates] bormant | ru:slackbook:tracking_updates [2013/11/15 09:38 (UTC)] – [Список рассылки обновлений безопасности] bormant | ||
---|---|---|---|
Строка 1: | Строка 1: | ||
====== Отслеживание обновлений ====== | ====== Отслеживание обновлений ====== | ||
- | <note important> | ||
- | ===== 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. | + | |
- | 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. | + | |
+ | | ||
+ | Поэтому важно своевременно устанавливать все заплатки для вашей версии Slackware, которую будем называть **-stable** (стабильной) веткой. | ||
+ | Ещё существует ветка **-current** (текущая), | ||
- | 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 | + | Поскольку многие зеркала доступны в паутине, наиболее распространённый путь -- получение обновлений через серверы |
- | the '' | + | Проект |
- | ways. While some mirrors offer web access, the most common ways of | + | Если не уверены, какое зеркало использовать, |
- | obtaining updates are via ftp and/or rsync servers. | + | Если рядом с вами есть крупный университет, |
- | project maintains a small list (organized by country) of known | + | Единственное существенное требование к зеркалу |
- | mirrors. | + | |
- | http:// | + | |
- | for suggestions. If you have a major university near you, there' | + | |
- | good chance that they offer a mirror of numerous open source projects, | + | |
- | and Slackware | + | |
- | 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. | + | |
- | + | ||
- | So how do you know when there are updates? | + | |
- | '' | + | |
- | find the latest changelogs for the -current and most recent -stable | + | |
- | branch on the Slackware Project' | + | |
- | version of Slackware, you'll need to check a mirror. | + | |
+ | | ||
+ | Наилучший способ -- посмотреть '' | ||
+ | Актуальные журналы изменений для текущей и последней стабильной веток доступны на сайте Slackware, но если используете более старую версию Slackware, придётся обращаться к зеркалам. | ||
< | < | ||
Строка 52: | Строка 32: | ||
Remove mention of HAL in the initial welcome email (mention udisks2 | Remove mention of HAL in the initial welcome email (mention udisks2 | ||
instead). | instead). | ||
- | a/ | + | a/ |
- | ===== Security Update Mailing List ===== | + | </ |
+ | ===== Список рассылки обновлений безопасности | ||
- | While the Slackware | + | |
- | not security fixes) occasionally, you're probably most interested in | + | Проект |
- | security fixes for vulnerabilities discovered after the -stable release. | + | Для подписки на список рассылки отправьте электронное письмо на < |
- | The Slackware | + | Управляющий (majordomo) будет рад добавить ваше имя в список, когда будут выпускаться обновления, он будет направлять вам рекомендации по электронной почте. |
- | updated packages for such serious issues. In order to subscribe to the | + | |
- | mailing list, send an e-mail to < | + | |
- | with the words **subscribe slackware-security** | + | |
- | The majordomo | + | |
- | packages are released, it will mail an advisory to you. | + | |
- | ===== Upgrading Slackware Versions ===== | + | |
- | Now that we've gone this far, you should feel reasonably competent in your | + | ===== Обновление |
- | ability to manage your Slackware | + | |
- | 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. | + | |
+ | | ||
- | Assuming you decide to do the upgrade, then the second thing you | + | И наконец, перед тем как начать, |
- | should do is read the '' | + | |
- | on your upgrade discs or a mirror. | + | |
- | 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 '' | + | ====== Навигация по главам ====== |
- | 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. | + | |
+ | **Предыдущая глава: [[slackbook: | ||
- | Since every new version of Slackware has a few differences, | + | **Следующая глава: [[slackbook: |
- | instructions here is not only futile but potentially misleading. | + | |
- | always consult the documentation included on your Slackware disks or your | + | |
- | favorite mirror. | + | |
- | ====== Chapter Navigation ====== | + | |
- | **Previous Chapter: [[slackbook: | + | ====== |
- | + | ||
- | **Next Chapter: [[slackbook: | + | |
- | + | ||
- | ====== | + | |
<!-- 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:// | + | * Источник: [[http:// |
<!-- Authors are allowed to give credit to themselves! --> | <!-- Authors are allowed to give credit to themselves! --> | ||
- | * Originally written by Alan Hicks, Chris Lumens, David Cantrell, Logan Johnson | + | * Авторы: |
<!-- * Contrbutions by [[wiki: | <!-- * Contrbutions by [[wiki: | ||
+ | * Перевод: | ||
<!-- Please do not modify anything below, except adding new tags.--> | <!-- Please do not modify anything below, except adding new tags.--> | ||
<!-- You must also remove the tag-word " | <!-- You must also remove the tag-word " | ||
{{tag> | {{tag> |