from the sidelines (Score: 3, Insightful) by pete@pipedot.org on 2015-07-26 22:14 (#FGZ2) with only scant knowledge of the implementation of systemd, i'll continue to be wary; I'll say, in large due to Linus' response to Kay Sievers requesting the kernel be patched to fix his own bugs.I don't hold Linus in too high regard because of his often unnecessary crass, but he usually makes a great point. I've read a couple examples of cockyness and ego, and for me that raises red flags for potential vulnerability or simply poor coding - not much is more dangerous than a programmer who believes they don't make mistakes. I'm open to counter-examples tho, i'm not anti-systemd because of some movement, perhaps its simply this Re: from the sidelines (Score: 1) by billshooterofbul@pipedot.org on 2015-08-03 17:06 (#GA5B) Getting yelled at for breaking a userspace app and or kernel debugging features is kind of a mark of honor. Alan Cox got reamed for breaking emacs a while back. Not wholly undeserved, but its kind of Linus' role to protect userspace from kernel devs and kernel devs from userspace. Its easy to get tunnel vision and only care about a particular deep logical problem and find a way to fix it, but in such a way as it breaks compatibility. Of course when egos are involved, sometimes people don't put the finest foot forward, but eventually cooler heads prevail and solutions are found. In Kay's case, it was a fight over boot params namespace. I kind of agreed with him on that, but the change they did make really killed kernel debugging, and so while he might have been technically correct, it was the wrong way to do that due to the impact.
Re: from the sidelines (Score: 1) by billshooterofbul@pipedot.org on 2015-08-03 17:06 (#GA5B) Getting yelled at for breaking a userspace app and or kernel debugging features is kind of a mark of honor. Alan Cox got reamed for breaking emacs a while back. Not wholly undeserved, but its kind of Linus' role to protect userspace from kernel devs and kernel devs from userspace. Its easy to get tunnel vision and only care about a particular deep logical problem and find a way to fix it, but in such a way as it breaks compatibility. Of course when egos are involved, sometimes people don't put the finest foot forward, but eventually cooler heads prevail and solutions are found. In Kay's case, it was a fight over boot params namespace. I kind of agreed with him on that, but the change they did make really killed kernel debugging, and so while he might have been technically correct, it was the wrong way to do that due to the impact.