SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Having been the only Linux admin of sorts at my former place of employment at my local community college, I can attest to why some of this might be helpful from a standards perspective.
DRBL, software I used for cloning lab systems among other things, was not something that was made to work with Slackware. It does work with Debian (Supposedly, I had issues with it), but I ultimately used CentOS.
In that case, it's a collection of various software put together in such a way to make the whole cloning job go smoothly. But this kind of setup can't really be replicated with relative ease when you have a bunch of people using different standards/methodologies. (This is just an example of course, I'm sure this could happen just as easily with other software.)
Additionally, some of the ease of use points are indeed of concern. While I learned Linux on Slackware and attest to it, it remains a hard sell for me to people that are new to Linux, because I'm supposedly known for my friends to use Slackware because I'm "into Linux hardcore", and so in that respect it's viewed as a hobby OS more than something to use widely. I don't agree with that attitude, but unfortunately it's often what prevails, and it's partly why I couldn't install Slackware and leave it for someone else to manage when I left, it's just not considered easy enough.
So, as others have pointed out, there are places where standards can help, but I don't think it's a particularly common concern. The harder sells I think are the ease of use points. While most of us use Slackware because we agree with the design decisions and see why they are done, there is naturally a lot of disagreement as to what's best.
Also, to claim LSB compliance you have to pay quite a lot to be certified.
Ignoring any official title requests could we at least have the symlink for ld-lsb.so.3 -> ld-linux.so.2 so that certain applications (namely Google Earth) work without any extra work.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.