GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
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.
Next to pulse audio, you might get more crap to your PC: systemd.
Systemd is often a serious topic of discussion. Is having systemd on your Linux system an issue?
wikipedia:
Quote:
As of 2015, many Linux distributions have adopted systemd as their default init system.[8] The increasing adoption of systemd has been controversial, with critics arguing the software has violated the Unix philosophy by becoming increasingly complex, and that distributions have been forced to adopt it due to the dependency of various other software upon it, including, most notably, the GNOME 3 desktop environment.
Should Systemd be removed in coming Debian distros?
No, SystemD is not evil. Many folks find it annoying, but annoying =/ evil.
There are a number of threads at LQ with detailed discussions about SystemD; the LQ Search will turn them up. I think you will find the answers to your question there.
Personally I can care less about the whole sysatemd crap.
Hell I can care less if it was made by Microsoft as long as it works I really dont care with these things.
Actually, I have come to like systemd ... ... because with it system configuration has become visibly more organized. Instead of relying on a bunch of core processes that don't talk to one another, you now have a (larger ...) group of them that do.
The systemd vs init debate never seems to go away, much like lilo vs grub.
Like many people, I resist change for the sake of change alone but if I can see
where change is needed,ie; is an obvious improvement and a benefit over something already
existing, then I will get on board.
I don't buy the argument that change is inevitable, not all changes have been good or
beneficial.
Is systemd an improvement? I will let those with more experience answer.
I don't mind systemd. It even has some advantages. It makes booting faster (and shut-down faster still) and I quite like the configuration files. They're easy to understand and write, which is more than you can say of init scripts. I don't like the binary journal though. Say you've just made an LFS and you can't boot it. With sysvinit, you can just boot with SystemRescue, mount the root partition and look in the logs to see what went wrong. With systemd you can't because only systemd-journalctl can read those logs.
But I really don't see why this subject arouses so much venom and hatred.
I don't mind systemd. It even has some advantages. It makes booting faster (and shut-down faster still) and I quite like the configuration files. They're easy to understand and write, which is more than you can say of init scripts. I don't like the binary journal though. Say you've just made an LFS and you can't boot it. With sysvinit, you can just boot with SystemRescue, mount the root partition and look in the logs to see what went wrong. With systemd you can't because only systemd-journalctl can read those logs.
But I really don't see why this subject arouses so much venom and hatred.
I'm not sure, either. "Rescue disks" that I have seen already include a binary logfile-reader.
One of the many things that the project attempted to do was to provide consistency in log-data formatting, as well as to conserve space. Production logs can grow by megabytes per second.
There are a number of threads at LQ with detailed discussions about SystemD; the LQ Search will turn them up. I think you will find the answers to your question there.
I don't use or like systemd - it's not my thing. But I don't subscribe to the idea that any kind of ideological/militant approach and/or boycott is going to weaken it in any way (never mind personal attacks directed at the developers) - likewise projects like Devuan don't really achieve anything and there are smaller Debian based Linux distributions which have made more headway in removing systemd, not to mention the many distributions and other operating systems which haven't adopted it - while Devuan seem to have just done a lot of talking, proselyting, speculating and investing in gaining a 'fan following' who are for the most part not developers and not really informed. Personally I think such groups/projects lack credibility and only strengthen the projects they oppose. And after all, systemd is a credible software project, rather than a distribution (or minor reworking of a distribution). If this had been another viable init system project vs systemd, it might have been taken more seriously.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.