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 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.