SoylentNews is people
SoylentNews
from the or-at-least-not-be-bothered-either-way dept.
[Ed's Comment: Not wishing to ignite yet another flame war regarding the adoption of systemd, I hesitated before publishing this story. However, although it is not an formal survey, it might still reflect the views of the greater linux user community rather than those who frequent this particular site. There is no need to restate the arguments seen over the last few weeks - they are well known and understood - but the survey might have a point.]
http://q5sys.sh has recenlty conducted a survey finding many Linux users may be in favour of systemd:
First off lets keep one thing in mind, this was not a professional survey. As such the results need to be taken as nothing more than the opinions of the 4755 individuals who responded. While the survey responses show that 47% of the respondents are in favor of systemd, that does not mean that 47% of the overall linux community is in favor of systemd. The actual value may be higher or lower. This is simply a small capture of our overall community.
Although the author questions the results could this be an indication that we're really seeing a vocal minority who don't want systemd while the silent majority either do or simply don't care? Poll results and the original blog post.
(Score: 2) by opinionated_science on Friday November 21 2014, @02:14PM
As I have mentioned before, opensuse had "init" wrappers to systemd for a few years now.
My major problem with systemd is the opaque logging, and slightly cryptic configuration.
But I don't complain because I am not not writing code - I'm a user.
A lot of people who are complaining about systemd dont't seem to realise what a mess the init.d stuff is. Is systemd the answer? I don't know but it has definitely speeded up boot times, on my desktop and laptop.
Furthermore, if you read the roadmap for systemd, there are some very cool things that can be done with it, that CANNOT be done with init.d scripts.
If it doesn't work for you, get together and write a wrapper script so that you can use the old init.d system That would probably be the best compromise.
I don't know if you feel it , but there is a war between corporate ownership and FOSS culture. We need the best tools for GNU/linux to prosper.
If you don't like how systemd is doing something , please submit a patch, or convince someone else to do so....
(Score: 1) by jmorris on Friday November 21 2014, @07:48PM
But I don't complain because I am not not writing code - I'm a user.
I am writing code. Two days ago I ran smack into systemd. Hear and despair:
I am interfacing an RFID reader via serial. Damned thing would not work. Open calls would throw errors unless I was root. Permisisons were right, selinux is long discarded so WTF? Google a bit and get reminded of the rules controlling tty type devices. The first user to open one owns it, that user can multiple open but not others, even in the right group. Ok, that clue lead, via fuser, to discover that gpsd was somehow installed and that it was claiming the freshly connected USB-Serial adapter. Fine. 'service gpsd stop' (Running Fedora 20) and it translated that to a twice as long invocation of systemctl... that at least was decent enough to warn about the sodomy that was coming. "Warning: systemd controls your horizontal, systemd controls your vertical. Systemd reserves the right to automatically restart this service on demand via socket activation." Ok, 'chkconfig gpsd off' should work. Same thing, another translation to a steaming pile of systemdctl and no difference. Systemd knows best.
And sure enough some damned thing keeps on fondling that gpsd socket. Why? Who the hell knows anymore, a modern Linux desktop is as inscrutable as Windows. But fondle it does and damned if systemd doesn't keep right on launching gpsd. So finally I pulled out the big gun and just did 'rpm -e gpsd' and for now systemd didn't reply with a "I'm sorry Dave, I'm afraid I can't let you to do that." How long until package management gets sucked into systemd? (Is Debian ready to be rpm based?)
So after a few hours lost to Freedesktop.org and PotteringOS foolishness I'm back to troubleshooting why my code doesn't talk to the reader... but that is my problem since the port is now open and sending/receiving bits. (Confirmed by null modem to a nearby server's spare serial port.)