So, you want to be a Slacker!? - Part three: The Slacker hanging on the branch
Posted 09-01-2021 at 07:29 PM by carriunix
As a final post about the "Slacker way" as I see it, let me write about branches and updates. One of the most frustrating things that happens with computer users is update the OS and break something in the system. "If I knew that will happen, I would have kept my old system", is the only thing we could think after that, obviously. It happens with all OS (Windows, MacOS and Linux), and more often, in those with short development cycles. That is, of course, instability. If an OS try to follow every hardware/library/app update, it will face a break here and there. It is not an flaw, it is a choice. Slackware Linux (personified in Mr. Volkerding in this case) made a different choice. The stable branch of Slackware is stable. Basically, the updates that the stable branch receive are security ones. All the movements to track technological developments are made in the "development" branch, Slackware-current. So, here comes the "one million dollar question": should I install the stable or current version of Slackware?
The answer, clearly, is: you are free to do whatever you want. But, let me present you some considerations.
I think that one should install Slackware-current in three situations: (i) if you want to be a tester, report problems, etc; (ii) if you need some applications that doesn't work with the last stable version (although a partial update could solve that) or if you have an incompatible hardware; (iii) if you want a system always updated and are not worried about eventual breaks that a development branch will bring. If you decide to use the current, your visits to LQ forum and newsgroup will be more frequent. Here and there you will face some problem. Even so, Slackware-current is more stable than many "stable" releases of other distributions. It is not like your system broke every day, but updates are more frequent. That is why you must follow the Change Log closely and upgrade the system (use slackpkg for this) frequently.
If every application that you use works fine on -stable, then keep it! Use it, mainly, because it works. And wait patiently for the next release. New kernels and new software releases can create some tension, some anxiety, for updates. Inform yourself about the real features added to these new versions. If nothing really important for you comes up, stay at the calm waters of stability. Let the Slackware's core team test, compile and pack these new versions for you in the next release. You probably have more important things to do and do not have their expertise. But, do not get it wrong: -stable is not for "beginners" or something like that. Have -stable installed is important if you are a Slackbuild maintainer, for example. If you are a professional system admin, with use Slackware servers, -stable is what you need.
Of course, you could choose one of the branches or you could have both! That is a very interesting idea to learn and use the best of the OS.
Independently of the branch that you use, -stable or -current, you must keep your system updated. Whatever the reason that convinced you to use that branch, it demands a updated system. In case of -stable, you must keep the security. In case of -current, you must keep the testing routine (and the security). With the slackpkg tool, keeping your system updated is quite simple. Just be sure that you understand the process to avoid break your system. A significant amount of reported breaks in Slackware systems result from slackpkg misuse. Again, I think this is the main idea to Slackers: know what are you doing.
Subscribe to the mailing lists (slackware-security is mandatory!) or RSS feeds to track the Change Log.
Enjoy your Slackware Linux system!
The answer, clearly, is: you are free to do whatever you want. But, let me present you some considerations.
I think that one should install Slackware-current in three situations: (i) if you want to be a tester, report problems, etc; (ii) if you need some applications that doesn't work with the last stable version (although a partial update could solve that) or if you have an incompatible hardware; (iii) if you want a system always updated and are not worried about eventual breaks that a development branch will bring. If you decide to use the current, your visits to LQ forum and newsgroup will be more frequent. Here and there you will face some problem. Even so, Slackware-current is more stable than many "stable" releases of other distributions. It is not like your system broke every day, but updates are more frequent. That is why you must follow the Change Log closely and upgrade the system (use slackpkg for this) frequently.
If every application that you use works fine on -stable, then keep it! Use it, mainly, because it works. And wait patiently for the next release. New kernels and new software releases can create some tension, some anxiety, for updates. Inform yourself about the real features added to these new versions. If nothing really important for you comes up, stay at the calm waters of stability. Let the Slackware's core team test, compile and pack these new versions for you in the next release. You probably have more important things to do and do not have their expertise. But, do not get it wrong: -stable is not for "beginners" or something like that. Have -stable installed is important if you are a Slackbuild maintainer, for example. If you are a professional system admin, with use Slackware servers, -stable is what you need.
Of course, you could choose one of the branches or you could have both! That is a very interesting idea to learn and use the best of the OS.
Independently of the branch that you use, -stable or -current, you must keep your system updated. Whatever the reason that convinced you to use that branch, it demands a updated system. In case of -stable, you must keep the security. In case of -current, you must keep the testing routine (and the security). With the slackpkg tool, keeping your system updated is quite simple. Just be sure that you understand the process to avoid break your system. A significant amount of reported breaks in Slackware systems result from slackpkg misuse. Again, I think this is the main idea to Slackers: know what are you doing.
Subscribe to the mailing lists (slackware-security is mandatory!) or RSS feeds to track the Change Log.Enjoy your Slackware Linux system!
Total Comments 0
