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.
I know, I know, we have here several French friends who will need soon new keyboards, because of spilling coffee - I apologize in advance for their loss.
I know, I know, we have here several French friends who will need soon new keyboards, because of spilling coffee - I apologize in advance for their loss.
The single biggest problem with the BSDs (in my experience) is their lack of hardware support. They simply do not match Linux when it comes to things like support for wifi cards out of the box.
If not for that, I'd probably have switched a long time ago. The BSDs are very well designed from the ground up. They're engineered as opposed to "cobbled together." Their documentation always fits. Sometimes in Linux, things can change before the documentation is updated and so you have to take information from a variety of sources to make it "fit" what you're trying to achieve, and other times there can be a bit of trial and error to get the result that what you want. This isn't the case with the BSDs. If you follow the documentation there is a 100% chance that it'll do what you expect.
While Slackware is counted among the Linux distributions which are closest to the "BSD way," it is still quite different. Try one of the BSDs in a VM and you'll quickly notice major differences.
In terms of outright flexibility, my opinion is that Slackware is unparalleled by any OS available today. It is truly multi/general purpose and comes with a powerful and practical suite of software out of the box.
The single biggest problem with the BSDs (in my experience) is their lack of hardware support. They simply do not match Linux when it comes to things like support for wifi cards out of the box.
If not for that, I'd probably have switched a long time ago. The BSDs are very well designed from the ground up. They're engineered as opposed to "cobbled together." Their documentation always fits. Sometimes in Linux, things can change before the documentation is updated and so you have to take information from a variety of sources to make it "fit" what you're trying to achieve, and other times there can be a bit of trial and error to get the result that what you want. This isn't the case with the BSDs. If you follow the documentation there is a 100% chance that it'll do what you expect.
While Slackware is counted among the Linux distributions which are closest to the "BSD way," it is still quite different. Try one of the BSDs in a VM and you'll quickly notice major differences.
In terms of outright flexibility, my opinion is that Slackware is unparalleled by any OS available today. It is truly multi/general purpose and comes with a powerful and practical suite of software out of the box.
While Slackware is counted among the Linux distributions which are closest to the "BSD way," it is still quite different.
Maybe the Slackware is closest with what "BSD way" was 25 years ago. Or 40?
Heck, even in this forum was lengthy explanations that "BSD-like" legend is, well... just a legend.
NOT that I'm against the "BSD way" !
Honestly, I would love Slackware to follow the "BSD way" by having also a powerful Ports system, with build and runtime dependencies resolution, supporting multiple remote binary packages repositories and plenty of shinny things which could be usually found in a BSD Ports system.
Yes, The BSD Way means also the dependencies resolution, with all its bells at neck.
Last edited by LuckyCyborg; 02-09-2022 at 06:34 PM.
Maybe the Slackware is closest with what "BSD way" was 25 years ago. Or 40?
Heck, even in this forum was lengthy explanations that "BSD-like" legend is, well... just a legend.
NOT that I'm against the "BSD way" !
Honestly, I would love Slackware to follow the "BSD way" by having also a powerful Ports system, with build and runtime dependencies resolution, supporting multiple remote binary packages repositories and plenty of shinny things which could be usually found in a BSD Ports system.
Yes, The BSD Way means also the dependencies resolution, with all its bells at neck.
If I had to guess, I would say the legend comes from the bsd inspired rc scripts and "Since [...] 1993, the Slackware Linux Project has aimed at producing the most "UNIX-like" Linux distribution out there"
I would say Slackware is indeed very BSD like, just not in the way many might imagine.
Last edited by khronosschoty; 02-09-2022 at 06:46 PM.
The single biggest problem with the BSDs (in my experience) is their lack of hardware support. They simply do not match Linux when it comes to things like support for wifi cards out of the box.
I completely agree! Slackware usually in most cases works out of the box for me on anything I try. However, I cannot say that for the BSDs. For example, sometimes OpenBSD cannot identify my SSD during installation. Thankfully on my secondary desktop OpenBSD plays well with the hardware; I've got a nice dual boot going with Slackware 15.0.
Slackware is superior with hardware identification compared to the BSDs.
The single biggest problem with the BSDs (in my experience) is their lack of hardware support.
...
They're engineered as opposed to "cobbled together."
Or perhaps the single biggest problem is the licence? And perhaps the hardware issue is a subproblem of that? Someone once put it to me very well: why would you want to share your work, if someone can just take it without contributing back? Like a corporation. Why would you want to contribute with passion, and a rich corporation gets your work for free and don't have to contribute anything, and can use the code as they want, and not even have to show it.
For more ideological minded people like myself, I was reminded on this very forum that switching to BSD would be extremely problematic, and go against the very fundamental principles that I like about GNU(/Linux) and what made it all possible in the first place.
I do like the idea of engineered, and I believe that is what GNU is trying with Hurd, haha, it's just taking awhile
Or perhaps the single biggest problem is the licence? And perhaps the hardware issue is a subproblem of that? Someone once put it to me very well: why would you want to share your work, if someone can just take it without contributing back? Like a corporation. Why would you want to contribute with passion, and a rich corporation gets your work for free and don't have to contribute anything, and can use the code as they want, and not even have to show it.
For more ideological minded people like myself, I was reminded on this very forum that switching to BSD would be extremely problematic, and go against the very fundamental principles that I like about GNU(/Linux) and what made it all possible in the first place.
I do like the idea of engineered, and I believe that is what GNU is trying with Hurd, haha, it's just taking awhile
It is kind of Ironic, how (at least in my mind), the gpl projects work in the corporate world, because, they don't REALLY want to share, they just want to "share".
[...]In a world without Gentoo, today all Slackers would have been masters in invoking systemctl ...
Well, I still am (or at least I'm closer to it than I ever wanted to be), "thanks" to all the RHEL/CentOS (plus the occasional SUSE & Ubuntu/Debian) servers I have to deal with at work on a daily basis ...
...Unless the systemd-haters prepare another
kdbus userspace until then this will effectively also mean that we will
not support non-systemd systems with udev anymore starting at that
point. Gentoo folks, this is your wakeup call.
Lennart
--
Lennart Poettering, Red Hat
I miss ye olde flamewars, when anger was rooted in a passion for quality code.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
