[SOLVED] Is 2019 Still Too Soon For Intelligent Assessment of SystemD?
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.
Exactly. Use whatever OS or init system that meets your needs. Live and let live.
It seems that this topic is akin to politics and religion. People really get fired up about this issue.
I guess it splits the people into those who understand the fundamentals of GNU/Linux including the freedom and choice aspect, and those who don't or don't care.
It is politics as well, and even religion for some. But "do one thing and do it well" IS POLITICAL, it's not inherent to code projects, it's the politics of GNU/Linux, and so is choice, it's policy. Both with long history and tradition in the GNU/Linux environment. That's just an example, but there are many policies deeply ingrained into the GNU/Linux environment (/people) and it's history and traditions.
Someone with a blatant lack of respect for all that, is causing issues, so it's natural to discuss systemd on a "political level", because it's highly political.
If Slackware ships systemd tomorrow the wannabe geeks wont even notice. They blindly run slackpkg anyway. The fanatics will instantly change their tune because BOB told them so and will prize "Slackware's systemd - the best in the world". And the few remaining Linux users will use the skills they already have.
I disagree, pretty much everyone who uses Slackware would notice. It would be clear from boot, and it would be clear from how certain hardware drivers were or weren't loaded [emphasis on "weren't" for me]. More to the point, maybe you want to flag if people would care. I think they would, primarily because Slackware appeals to the kind of person who appreciates older technological principles and to the kind of person who is inherently, as a result, suspicious of newer technologies unless proven harmless and under control of the user.
systemd has not been proven harmless, neither have the intentions of its developer[s]. If anything, there is more reason to be suspicious of systemd than not. Slackware has been described as the distribution of the "cyber-luddite", and such people are way more trustful of long-tested, stable technology. Remember that each distro is not a mere distro but a mindset and an ethic, and for systemd to be integrated into Slackware would be to change the very ethos of the distribution. If Slackware were going to adopt systemd, it may as well call itself something else, because it would effectively be like having HRT, changing its gender and 'identifying' as another distribution. But this is all academic seeing as Eric has already said recently that there is "no need" to adopt systemd in Slackware.
Slackware is very good at remaining true to itself, and that's one of the things that makes it so long-lasting and healthy. And that's a lesson that goes beyond just computing.
Quote:
Originally Posted by ivandi
The hard truth is that unless you come up with better code systemd is here to stay.
You are absolutely correct on this, and if it weren't systemd it would be something similar. Poettering just got there first. Something like systemd was inevitable because it's a human trait to make technology increasingly controlling. It doesn't mean that such technology has to be adopted by everyone.
Last edited by Lysander666; 08-24-2019 at 07:50 AM.
I didn't even know they used it. I haven't used Knoppix in donkey's years but I have fond memories of it. My first Linux (Red Hat 6) was so messed up by the friend who installed it for me that it was completely unbootable. So he gave me a Knoppix CD to use to straighten things out, which turned out to be easier than I expected. In those days Knoppix was probably the only live distro around.
(...) So he gave me a Knoppix CD to use to straighten things out, which turned out to be easier than I expected. In those days Knoppix was probably the only live distro around.
Here, the best known live distro is Alien Bob's Slackware Live Edition!! :-)
It is still actively maintained (latest is dated 2019-07-13) and closely follows Slackware current (an easy way to test Current on any PC). It provides persistence, optionally encrypted.
To the best of my knowledge, it was the first to use the regular kernel "OverlayFS" union filesystem, instead of aufs which is used in many live distros (including Knoppix?)
Please Eric correct these links if they are not the preferred ones (especially the doc which points to a page dated Nov 2015 -- is it still the good one?)
Slackware is very good at remaining true to itself, and that's one of the things that makes it so long-lasting and healthy. And that's a lesson that goes beyond just computing.
Indeed! I've been a Slacker since 2004(version 10.0). Patrick continues to keep Slackware simple, robust and secure.
Praise Bob.
Distribution: Slackware/Salix while testing others
Posts: 1,718
Rep:
Quote:
Originally Posted by ivandi
This thread resembles the reports my wife writes for the government. Somehow she is able to write pages without saying anything. And they like it.
If Slackware ships systemd tomorrow the wannabe geeks wont even notice. They blindly run slackpkg anyway. The fanatics will instantly change their tune because BOB told them so and will prize "Slackware's systemd - the best in the world". And the few remaining Linux users will use the skills they already have.
Cheers
Good to see the Slackware threads are still your catnip.
Distribution: Slackware/Salix while testing others
Posts: 1,718
Rep:
Quote:
Originally Posted by Lysander666
I disagree, pretty much everyone who uses Slackware would notice. It would be clear from boot, and it would be clear from how certain hardware drivers were or weren't loaded [emphasis on "weren't" for me]. More to the point, maybe you want to flag if people would care. I think they would, primarily because Slackware appeals to the kind of person who appreciates older technological principles and to the kind of person who is inherently, as a result, suspicious of newer technologies unless proven harmless and under control of the user.
systemd has not been proven harmless, neither have the intentions of its developer[s]. If anything, there is more reason to be suspicious of systemd than not. Slackware has been described as the distribution of the "cyber-luddite", and such people are way more trustful of long-tested, stable technology. Remember that each distro is not a mere distro but a mindset and an ethic, and for systemd to be integrated into Slackware would be to change the very ethos of the distribution. If Slackware were going to adopt systemd, it may as well call itself something else, because it would effectively be like having HRT, changing its gender and 'identifying' as another distribution. But this is all academic seeing as Eric has already said recently that there is "no need" to adopt systemd in Slackware.
Slackware is very good at remaining true to itself, and that's one of the things that makes it so long-lasting and healthy. And that's a lesson that goes beyond just computing.
You are absolutely correct on this, and if it weren't systemd it would be something similar. Poettering just got there first. Something like systemd was inevitable because it's a human trait to make technology increasingly controlling. It doesn't mean that such technology has to be adopted by everyone.
Great points, it's more likely the people who blindly accepted systemd are of the group/crowd mentality of ...I turn on the computer and use what loads. Or on many computers I wake up the device and use whats there. Those who are against/apprehensive/suspicious etc... of systemd are usually the ones who like to dig deeper and understand more.
"This bypasses systemd's interference with many system components and reduces the complexity of the overall system."
I love it! Knoppix was part of my toolbox for a very long time (until I discovered Alien Bob's live Slackware versions). I'm off to download Knoppix 8.6 right now. Don't fret AB. Your Slackware live distro will still be my #1!
Slackware is very good at remaining true to itself, and that's one of the things that makes it so long-lasting and healthy. And that's a lesson that goes beyond just computing.
Slackware is very good at remaining true to itself, and that's one of the things that makes it so long-lasting and healthy. And that's a lesson that goes beyond just computing.
So far the low number of "cyber-luddites" supporting the project teaches the lesson that usability is more valuable than philosophy.
Thanks for the links but I was already familiar with the nightmare on Debian of installing no-systemd.deb and removing systemd. I just didn't know enough to fix the nightmare and gave up in disgust.
Creating this thread did lead me to some newer videos and papers that have clarified for me that systemd has very little to do with SOHO Desktop, which is apparently why the only plus I've ever witnessed, and even then only on some systems with some hardware, is the oft quoted but rarely realized "faster boot times" which I don't give a hoot about anyway.
Enterprise Server Administration however does seem to have a longer list of benefits to enjoy from systemd, which is beginning to get through to me more of why the switch to systemd was nearly universal and so sudden. Just as most schools require a uniform program if not also the underlying system upon which it was developed so that a teacher/professor does not have to convert to a format that each and every individual student prefers, Enterprise values uniformity. They always have, even to ridiculous degrees. (Aside: I read that IBM employees were once "called up on the carpet" for not wearing garters on their approved socks! ) Apart from the ridiculous there is the consonant advantages of system-wide upgrades and improved security on every single workstation accomplished extremely quickly. I have to admit that this is not trivial nor is it the end of the benefits to Enterprise.
I'm no longer even a candidate for really large business systems, so I don't really "have a dog in that race". The largest system I ever admin'd was just under 200 workstations and these days I'm down to roughly a dozen since I'm all but fully retired.
Anyway judging from the gist of this thread and the reception, or lack thereof, of the original video here's one that gets a lot more specific about the value to Enterprise. Maybe 1 or 2 will actually watch it.
Thanks for the links but I was already familiar with the nightmare on Debian of installing no-systemd.deb and removing systemd. I just didn't know enough to fix the nightmare and gave up in disgust.
That wasn't really the point. It was more to give you his reasons for making the change, rather than the difficulties he faced... which is why the Youtube link starts 17 minutes in... that's the part of the video where he gives his reasons for switching away.
Quote:
Originally Posted by enorbet
Creating this thread did lead me to some newer videos and papers that have clarified for me that systemd has very little to do with SOHO Desktop, which is apparently why the only plus I've ever witnessed, and even then only on some systems with some hardware, is the oft quoted but rarely realized "faster boot times" which I don't give a hoot about anyway.
Strangely enough, slow boot times on real hardware was one of Mr. Knopper's reasons for removing systemd.
I could tolerate systemd if it would have been developed as an opt-in framework, I'd opt out and don't bother.
Speaking of its development, initiated and mainly dictated/driven by that failed endeavor (sold out), what was the name? RedHat..., I put systemd in the same boat with pulseaudio, same non-transparency, low quality code and bad documentation.
As for features, I watched half of the video enorbert posted "--- Systemd - The Good Parts --- " , got bored and stopped, couldn't find anything interesting, other than the dbus stuff (really useful?), nothing you couldn't easily resolve with some basic bash scripting.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.