Quote:
Then there was also usbmount, mtools and autofs, any of which could have easily been tweaked for roll out in a public library. Quote:
Quote:
|
Quote:
Quote:
|
"If you want to learn RedHat, learn RedHat. If you want to learn linux, learn Slackware."
|
Quote:
|
Quote:
What he was getting at with the quote is that Slackware does things in standard ways, it teaches you to use standard tools and sensible, portable techniques of administration. Certainly it's not exactly the same as LFS or Gentoo or OBSD OSolaris or what have you, but it knows it's a member of the same family and it behaves in a manner consistent with the family. Other linux distros have tended to fall into the trap of 'differentiation' - doing things differently for the sake of marketing. Slackware has not. So when you learn Slackware, in a real sense you are learning the core of *nix in general. Shell scripting, text editing, system administration are not that different between these systems. When you learn other distros, you are much more likely to wind up learning to just click their proprietary tools, and call support if something goes wrong. When you find yourself on a closely related system with different proprietary tools, you are even more lost than before! When you have problems you have no understanding of the system architecture or the system tools, you cannot diagnose the problem, and even if you could you would have no idea how to fix it. Computers should empower people, not the opposite. |
Slack is the only distro I use that really doesn't encourage 'black boxing' at all. I also use Gentoo, and it's superb, but as an administrator you tend to get good at deciphering the mighty portage. Unless you learn to write ebuilds, you won't learn much about where everything goes.
Even Arch for all its pared down simplicity tends to push you towards some copypasta with configuration, especially since systemd came along. The community is so large and the tools so good, you will seldom have to think about writing service files or PKGBUILDS. In many ways it's a sign of how successful it is. I learnt more about scripting and administrative basics playing with Slack's beautiful and simple package manager. Forcing the user to do some simple jobs after providing them with a useful and fully featured install is a great way to learn. Likewise I learnt a lot more about init because I did not have the service handler script to rely on. These are great things. |
Quote:
Quote:
Quote:
Quote:
Just because someone doesn't want to learn Slackware's methods doesn't mean they are learning how to "just click their proprietary tools". It isn't that everything else is different to Slackware it is that Linux offers a wide variety of choice and Slackware and its methods are one of those choices. For a thread based on a discussion about systemd, and the overall systemd discussion throughout LQ is based on a loss of choice the suggestion that offering people choice and that choice means they won't learn and is a bad thing strikes me as rather backward. Quote:
|
Computers are tools that get you from A to B. Empowering people would be letting them getting to B as fast and as easy as they can.
|
Quote:
|
Quote:
United we stand divided we fall (btw I am not a unionist by any stretch of the imagination). |
Quote:
|
Quote:
|
Quote:
|
Mass exodus? I recall similar talk when GNOME was dropped. I learned a new way, and continued using Slackware. If Slackware uses systemd then I will learn a new way and continue using Slackware. There is more to Slackware Linux than GNOME or systemd.
|
Quote:
I view it as a arrogant behavior. |
All times are GMT -5. The time now is 02:04 AM. |