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: 5, Insightful) by frojack on Thursday November 20 2014, @10:14PM
Where was this poll posted? I certainly never heard of its existence.
No, you wouldn't have, and neither did I.
Unless you happen to be on a site where the issue was actively discussed, you just don't run into these things.
Polls are put up, the troops are alerted, mass voting begins, with the usual mass-stuffing of ballots, favored group is all in ahead of time. When it looks like the voting is slipping to the opposition, the voting is closed.
Having just converted (fresh install) from an older release to a new one with systemd I see absolutely no improvement, stability, speed, or lower memory utilization. No obvious degradation either, until I want to do something like starting services or sucn
I do a lot more digging through man pages to find out how to do simple things. Mostly my distro wires the old commands into systemd , but not all of them.
So I see no benefit what ever. Simply a new learning curve.
No, you are mistaken. I've always had this sig.
(Score: 2) by emg on Thursday November 20 2014, @10:20PM
True. Someone asked me today how to run a script at startup, and I immediately said to just call it from /etc/rc.local.
Except we then discovered their new OS has systemd, and /etc/rc.local has a comment saying something along the lines of 'don't even think of calling stuff in here, because systemd makes things so much easier with unicorns and rainbows!'.
So we've no idea how to do something as simple as running a script at startup any more.
(Score: 2) by Konomi on Thursday November 20 2014, @11:00PM
You can redirect systemd users to this: How can I make a script start during the boot process? [archlinux.org] seems pretty strait forward.
(Score: 3, Informative) by Anonymous Coward on Thursday November 20 2014, @11:10PM
That's far more complex than adding just a line or two to /etc/rc.local. It's a huge step backward.
(Score: 2) by FatPhil on Friday November 21 2014, @08:53AM
Why doesn't it work? Is it command line parameters ("/path/to/script.sh") being passed to the program ("/bin/sh") that don't work? Do I conclude that the program may not take any command line parameters? The power of unix-alikes is the power of the command line, the power to parameterise things. If programs may simply run, be launched, and only do one thing, they're no better than icons on a desktop which you click to activate - they're nothing but a "do it" button. What if I want the program started with more verbose debug logging enabled? Can I not add the "-v" switch to the execstart line?
This sounds like a massive step backwards in user-friendliness (for those users who wish to be in control of their systems, rather than just click "do it" buttons).
Great minds discuss ideas; average minds discuss events; small minds discuss people; the smallest discuss themselves
(Score: 0) by Anonymous Coward on Friday November 21 2014, @12:17PM
I think I have figured it out. If you have a .sh to launch on init with parms then you create a second .sh to call the .sh required with the parms needed. Then add a service in systemd/system to that intermediate .sh
(Score: 0) by Anonymous Coward on Friday November 21 2014, @09:52PM
RTFM you noobs...
(Score: 0) by Anonymous Coward on Thursday November 20 2014, @11:01PM
Jesus Christ. Are you going to do the right thing and switch to FreeBSD?
(Score: 0) by Anonymous Coward on Friday November 21 2014, @08:02AM
Jesus Christ will never switch sides. Suffering it is.
(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.)