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.
For example before there used to be more admins required for all the servers. Now 1 admin is required for many servers using vmware/virtualbox. Hence, less admins required for hire.
What makes you thinking that you that you need less admins for virtual machines than for physical?
What makes you thinking that you that you need less admins for virtual machines than for physical?
Through 1 server you can control various servers across the world using vm remotely. So it makes sense to hire less admins to do the job. Also, with increased automation... there will be less time spent on configuring the system... hence again less need for admins. Am I not correct? Please enlighten me again if I am not correct...
What worries me most about Slackware's future is not systemd, it is secure boot. Today, when someone tells you about "security" ask them which side of the prison bars you are on and who has the keys. You'd be surprised at the answer.
There has been spread a lot of FUD about Secure Boot, I personally don't think it is a bad thing, not in its current form.
But anyways, Secure Boot is something that lies outside of Linux, you can simply avoid it by disabling it and have not to bother about it at all.
This is not true for systemd, it is a thing inside the Linux community, where one entity tries to force their standards on anyone else, regardless if that is sane and regardless the collateral damage that is done with that. If Linux has to follow the Red Hat standards in the future in opposite to being Unix like (where its roots come from and what has made it like it is), or at least let the developers/users choose their standards for themselves, it may be time to change to BSD.
I hope I don't have to, I really like Slackware, but I like it because it is like it is and a change to systemd would be pretty hard for me to accept.
However, the influence of their employer is so big that these products are forced upon the wider UNIX community and at some point it will be "assimilate or die". I hope we (Slackware) will find a way where we do not have to assimilate but still manage to keep the distro working.
Any chance Slackware might end up on a BSD kernel some time in the future? That's a question I wanted to put to Pat Volkerding for his interview.
Thanks for your numerous answers. According to them, I can only draw the following conclusion. In order to remain a happy Linux sysadmin, I would only have to 1) purchase a Slackware subscription and 2) throw Lennart Poettering into the nearest active volcano. Correct me if I'm wrong.
That's pretty doubtful, but the BSD userspace is looking better and better.
Shame! it would take a lot of work though. Slackware and the BSDs hit a sweet spot for sure. I like the way Slackware people and NetBSD people plug away quietly improving their OSes. No big heads trying to make a name for themselves by *improving* the Unix philosophy.
Thanks very much for the answer anyway! I'll do my best to get some money to you this year. It's been a tight few years in Ireland. Can't see how we can remain at the bottom for much longer. Fingers crossed!
As far as I understand, mostly GNOME stuff is concerned by systemd. I admit I've been a GNOME user for a few years, on CentOS, RHEL and Ubuntu, but decided to abandon it after fiddling around with GNOME3 for about ten minutes (the time it took to find out that there is indeed no Power Down button). I read Patrick Volkerding's statement about GNOME exclusion, it made me laugh and I totally understand his point of view.
For the last half year or so, I've been mostly working on a heavily modified Debian stable with KDE 4.4, and everything works perfectly. Though secretly I've always been a fan of XFCE's manner of doing things, only I didn't use for day to day work because of a few - sometimes - tiny missing bits I need for work. Right now, I'm busy writing SlackBuild scripts for the latest XFCE 4.10 that looks very appealing to me, plus it seems to have all the bits (more or less) I need for productive work.
But XFCE depends increasingly on GNOME libs, and that's where I'm really concerned. It would really piss me off to migrate my machines - and eventually those of my clients - to a healthy mix of Slackware and XFCE, only to see this great alternative desktop go down the drain in a future not that far away.
We still have the current sources for udisks, upower, and everything else that's not in systemd and such right?
As far as going with BSD's Userspace, +1 here if it can be done.
And as far as Slackware's developers... Slackware has a few developers, some official, but there's always the thousands of unofficial developers who could be enticed from other distributions to help port BSD-Userpsace to Linux. I seriously doubt all distributions out there will side with systemd if enough resistance can be met against it.
That's pretty doubtful, but the BSD userspace is looking better and better.
Damn right. Personally I love bsdtar. Thanks for including it in Slackware. I know it comes with libarchive but some distros (e.g. Debian) put it in a separate package so that it isn't always installed by default.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.