On Jul 8, 2014, at 7:58 AM, Reindl Harald h.reindl@thelounge.net wrote:
and the next one talking before try to get informations there is no monolithic daemon damned
there is one project with one source tree maintaining a lot of daemons and binaries - so be quite before you tried to learn some basics
Generally when people get personal I figure I must have hit a nerve.
I must have hit a nerve.
I didn't say it was windows-like. I said it was more windows-like than I was comfortable with. Even with multiple daemons, It's still not very transparent, somewhat incomrehensible, documented poorly while still managing to have voluminous documentation, dumps stuff everywhere, and is just generally annoying.
Even its sysv compatibility is incomplete. It runs sysv scripts, but in such a way as to break any but the simplest. I've run into situations where I've actually had to make a systemd unit because it broke the script, and I couldn't fix it. The script was fine, ran perfectly if you just ran it, and systemd did... *something*... to it. I still haven't figured out what. And debugging is an absolute pain.
And that's all I'm saying in response to you. Keep this up and my killfile will have one more entry.
--Russell
On Tue, 8 Jul 2014 08:05:07 -0700 Russell Miller duskglow@gmail.com wrote:
Generally when people get personal I figure I must have hit a nerve.
I must have hit a nerve.
I didn't say it was windows-like. I said it was more windows-like than I was comfortable with. Even with multiple daemons, It's still not very transparent, somewhat incomrehensible, documented poorly while still managing to have voluminous documentation, dumps stuff everywhere, and is just generally annoying.
Even its sysv compatibility is incomplete. It runs sysv scripts, but in such a way as to break any but the simplest. I've run into situations where I've actually had to make a systemd unit because it broke the script, and I couldn't fix it. The script was fine, ran perfectly if you just ran it, and systemd did... *something*... to it. I still haven't figured out what. And debugging is an absolute pain.
And that's all I'm saying in response to you. Keep this up and my killfile will have one more entry.
We don't care in facts. We just believe. So if you don't believe in systemd and Poettering, go away. We make religion, not technology.
Best Regards Oli
Oliver Schad wrote:
On Tue, 8 Jul 2014 08:05:07 -0700 Russell Miller duskglow@gmail.com wrote:
Generally when people get personal I figure I must have hit a nerve.
I must have hit a nerve.
I didn't say it was windows-like. I said it was more windows-like than I was comfortable with. Even with multiple daemons, It's still not very transparent, somewhat incomrehensible, documented poorly while still managing to have voluminous documentation, dumps stuff everywhere, and is just generally annoying.
Even its sysv compatibility is incomplete. It runs sysv scripts, but in such a way as to break any but the simplest. I've run into situations where I've actually had to make a systemd unit because it broke the script, and I couldn't fix it. The script was fine, ran perfectly if you just ran it, and systemd did... *something*... to it. I still haven't figured out what. And debugging is an absolute pain.
And that's all I'm saying in response to you. Keep this up and my killfile will have one more entry.
We don't care in facts. We just believe. So if you don't believe in systemd and Poettering, go away. We make religion, not technology.
Right. Can we get him to stop Peottering around in our gardens, and go play in one that does not affect so many people negatively?
mark
On 07/08/2014 11:05 AM, Russell Miller wrote:
On Jul 8, 2014, at 7:58 AM, Reindl Harald h.reindl@thelounge.net wrote:
and the next one talking before try to get informations there is no monolithic daemon damned
there is one project with one source tree maintaining a lot of daemons and binaries - so be quite before you tried to learn some basics
Generally when people get personal I figure I must have hit a nerve.
I must have hit a nerve.
I didn't say it was windows-like. I said it was more windows-like than I was comfortable with. Even with multiple daemons, It's still not very transparent, somewhat incomrehensible, documented poorly while still managing to have voluminous documentation, dumps stuff everywhere, and is just generally annoying.
Even its sysv compatibility is incomplete. It runs sysv scripts, but in such a way as to break any but the simplest. I've run into situations where I've actually had to make a systemd unit because it broke the script, and I couldn't fix it. The script was fine, ran perfectly if you just ran it, and systemd did... *something*... to it. I still haven't figured out what. And debugging is an absolute pain.
I am also struggling with this and the HIPL code (on F20). If you just start the services, it takes about 5 min to complete. If you just run the programs and tell them to drop into the background it is a handful of seconds. Strip out comments from the script and it starts right up with systemctl. Huh? What is going on? I was told that systemctl does seem to try and make 'sense' out of comments...
And that's all I'm saying in response to you. Keep this up and my killfile will have one more entry.
--Russell _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 07/08/2014 08:05 AM, Russell Miller wrote:
On Jul 8, 2014, at 7:58 AM, Reindl Harald h.reindl@thelounge.net wrote:
and the next one talking before try to get informations there is no monolithic daemon damned
there is one project with one source tree maintaining a lot of daemons and binaries - so be quite before you tried to learn some basics
Generally when people get personal I figure I must have hit a nerve.
I must have hit a nerve.
I didn't say it was windows-like. I said it was more windows-like than I was comfortable with. Even with multiple daemons, It's still not very transparent, somewhat incomrehensible, documented poorly while still managing to have voluminous documentation, dumps stuff everywhere, and is just generally annoying.
Even its sysv compatibility is incomplete. It runs sysv scripts, but in such a way as to break any but the simplest. I've run into situations where I've actually had to make a systemd unit because it broke the script, and I couldn't fix it. The script was fine, ran perfectly if you just ran it, and systemd did... *something*... to it. I still haven't figured out what. And debugging is an absolute pain.
And that's all I'm saying in response to you. Keep this up and my killfile will have one more entry.
On OpenSUSE, my trick for "disabling" systemd in the init script, is to rename systemctl at the start and put it back at the end. There is an included script (functions) look for it and if not found allows good ol' sysV to do it's thing. I expect It's done the same way for RHEL/Centos.
Just sayin'
On Tue, Jul 08, 2014 at 08:05:07AM -0700, Russell Miller wrote:
And that's all I'm saying in response to you. Keep this up and my killfile will have one more entry.
Please stop replying to non-list subscribers in Cc: fields. Harald was removed from this list years ago for, well, the reason should be quite obvious. When you group reply to his crap you are just drawing him back into the discussions.
Thanks,
John
On Jul 8, 2014, at 1:03 PM, John R. Dennison jrd@gerdesas.com wrote:
On Tue, Jul 08, 2014 at 08:05:07AM -0700, Russell Miller wrote:
And that's all I'm saying in response to you. Keep this up and my killfile will have one more entry.
Please stop replying to non-list subscribers in Cc: fields. Harald was removed from this list years ago for, well, the reason should be quite obvious. When you group reply to his crap you are just drawing him back into the discussions.
I don't feel bad about being tricked. It happens. When I see the mailing list as a recipient, even as a CC, I assume that it went to the list. I have no way of seeing the member list.
However, I think I may accelerate his entry into my killfile, in that case.
--Russell