DebianThis forum is for the discussion of Debian 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.
SystemD is fully Gnu compliant, it is specifically released under the LGPL 2.1 license. Wherever you read it doesn't comply with the GNU, GPL needs to get their facts straight.
There's a huge difference between good, and not compliant. Sure, systemd is junk, but it complies with GNU & FSF guidelines.
SystemD is fully Gnu compliant, it is specifically released under the LGPL 2.1 license. Wherever you read it doesn't comply with the GNU, GPL needs to get their facts straight.
There's a huge difference between good, and not compliant. Sure, systemd is junk, but it complies with GNU & FSF guidelines.
Protests to the contrary notwithstanding, SystemD in Debian does indeed seem to be a Done Deal. Wishful thinking is seldom a foundation for reasonable action.
I'm running Debian Sid on that computer over there.-------------------> I have reconciled myself to the idea that I must learn SystemD. Fortunately, there are a number of excellent tutorials on YouTube.
I am not a fan of SystemD for a number of philosophical reasons, but SystemD works (that is perhaps its most annoying characteristic), and I think it very unlikely that Debian or any other distro that has moved to SystemD will look back.
I am not a fan of SystemD for a number of philosophical reasons, but SystemD works
Not particularly well. I have a number of Ubuntu-using friends whose systems haven't been able to shut down cleanly for months, thanks to systemd. At work we've had problems with CentOS7 not logging certain events during system startup and not letting us properly initialize RAID controllers before attempting to mount their filesystems, both thanks to systemd.
A few days ago I overheard a coworker mutter "come on systemd, that worked just five minutes ago" and then later "I'm going home, I can't fight with systemd anymore today". That means a task was left undone because of systemd.
There's a growing number of security vulnerabilities introduced by systemd, and the development team's attitude towards fixing them has left something to be desired.
If that's "working", then we'll have to agree to disagree about the threshold of "working".
Not particularly well. I have a number of Ubuntu-using friends whose systems haven't been able to shut down cleanly for months, thanks to systemd. At work we've had problems with CentOS7 not logging certain events during system startup and not letting us properly initialize RAID controllers before attempting to mount their filesystems, both thanks to systemd.
A few days ago I overheard a coworker mutter "come on systemd, that worked just five minutes ago" and then later "I'm going home, I can't fight with systemd anymore today". That means a task was left undone because of systemd.
There's a growing number of security vulnerabilities introduced by systemd, and the development team's attitude towards fixing them has left something to be desired.
If that's "working", then we'll have to agree to disagree about the threshold of "working".
Agreed. It functions at a level adequate to be able to usually make everything boot. However, it's far from what I'd call "just works". And given how the development team seems only to care about adding "features" that have nothing to do with being an init process, not fixing the core functionality, I don't really ever see it "just working".
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.