search for: grokkable

On Tue, Oct 16, 2018 at 09:25:15AM -0500, Valeri Galtsev wrote: > Hoping to not offend proponents of systemd/firewalld... Perhaps if you weren't spreading misinformation, we wouldn't be offended? > Linux kernel is already containing chunks of code related to > systemd/firewalld and friends. One can disable stuff during kernel build, > but the result it still is not like the

...dollar company (AWS). SuSE Enterprise might be the best counter example here. Also, while EL6 did move from original init to upstart, that's somewhat beside the point. Almost none of the advanced features from upstart were used, and - crucially - the startup sequence was still handled with grokkable, imperative scripts. The jump from EL6->EL7 was night and day compared to EL5->EL6. -jc

...tually package the Red Hat init scripts as /etc/rc.d/init.d/, because /etc/init.d is a symlink, while on debian it is the actual location, and if you weren't careful, your package would create an /etc/init.d directory and suddenly it's not even found by the init system. Oh, and as for 'grokkable' shell scripts used by init, they bear only a passing resemblance between distros, they even differed between releases of the same distro, making it so you had to learn a different weird init system for each distro. Heck, there was even an argument about which shell they're run with. And...

Valeri Galtsev wrote: > On 10/17/18 7:55 PM, Warren Young wrote: <snip> >> Benno Rice is right: Lennart Poettering gets stuff done. Because he's funded. And I strongly suspect that a lot of that funding comes from M$'s interest in Upstream. <snip> > > With all due respect, many people just stopped offering any argument > about systemd, and simply fled