Originally posted by sdack
View Post
Announcement
Collapse
No announcement yet.
Systemd Is Launching Its Own Conference
Collapse
X
-
-
Originally posted by jb.1234abcd View PostDistrowatch.com systemd poll results (Jul 2015)
I use systemd and like it: 787 (30%)
I use systemd and dislike it: 318 (12%)
I am not using systemd and plan to use it: 111 (4%)
I am not using systemd and plan to avoid it: 1170 (44%)
Other: 260 (10%)
Well, that's 12% + 44% = 56% against systemd.
It's time to drop that trash ...
Comment
-
Originally posted by dvdhrm View Post
The conference website clearly states that the 96euro are gladly sponsored for community contributors. But please bear in mind that the conference needs to pay for catering, rooms, evening events, organizers, inviting speakers, and more. 96euro (including VAT) doesn't seem overly expensive for 3 full days covered.
Comment
-
Originally posted by jb.1234abcd View PostDistrowatch.com systemd poll results (Jul 2015)
Well, that's 12% + 44% = 56% against systemd.
Speaking for myself, I really appreciate rich process management features of systemd (yes, it can set priority, real-time scheduler, limits, seccomp filter of syscalls, etc). As well as ability to deal with various process failures in ways I need to mitigate issues in automatic systems running without human supervision and it even able to provide watchdog facilities to critical processes. In fact RH did a good job. And those like you should shut up unless you can offer something comparable to those who actually builds systems. But, sure, you fail to see any use cases beyound your dumb ego and your silly PC near you. However, since debian switched to systemd I got to love using it for embedded designs. It really saves me a lot of time on custom low level system coding. I do think it is cool.Last edited by SystemCrasher; 30 July 2015, 06:19 PM.
- Likes 1
Comment
-
Originally posted by SystemCrasher View PostAnd those like you should shut up unless you can offer something comparable to those who actually builds systems.
They did write code to do something comparable to all you cite: "set priority, real-time scheduler, limits, seccomp filter of syscalls {...} deal with various process failures in ways {needed} to mitigate issues in automatic systems running without human supervision {...} provide watchdog facilities to critical processes"
...well, at least as long as for "write code" you accept the definition "wrote a horrible non-portable unread mess of non standard shell code that is going to break as soon as someone either tries to fix a bit somewhere or use it as a template to build a new thing or port or move it to a different installation of even the same distro".
They mostly cry because their mess doesn't work anymore and they need to re-write it yet again.
The fact that, with modern software like systemD's PID1, upstart, etc. you can do all the same with simple declarative text file, that's easy to read/understand/edit (the whole point of being declarative text) and that it's possible to port it and move it around (systemd runs BOTH on my openSUSE powered desk- / and lap-tops AND on my SailfishOS powered phone) ... is completely lost on them.
Meanwhile...
Originally posted by SystemCrasher View PostIn fact RH did a good job.
RH use it and did a good job. As did openSUSE and SailfishOS, as I've mentionned above. It works, it's becoming a standard.
I'm happy that it's there, even if it means that I need to rewrite part of my own ugly shell code. At least the result of the rewrite is going to be much cleaner and portable.
Originally posted by SystemCrasher View PostHowever, since debian switched to systemd I got to love using it for embedded designs. It really saves me a lot of time on custom low level system coding. I do think it is cool.
Comment
Comment