"A second point is that it is easier to feel comfortable on the system, because the whole thing is consistent and easy to understand, provided you take some time and learn about the concepts." - very true. its the problem that most people moaning about systemd are out of their comfort zone and mostly shouting from ignorance of what systemd is and does.
"many" ??? just a few and as they are generally ACs, they are probably the same person. what are they going to do when FreeBSD implements their own version of systemd?
"The notion that BBs competitors should prop up the dying BB platform in some notional sense of fairness is stupid." - are Netflix et al really BB competitors, i would have thought that was Apple, Samsung etc? Anyway he's just saying similar to what others have said about wanting MS Office being able to run natively on other platforms but he is just spouting from another perspective.
"The only losers in these scenarios seems to be the rich 1%ers who can afford ocean front property" - as much as i'm with you on that, a lot of the worlds important cities are on the waters edge, losing an importatn city could cause all manner of problems for that country and globally if its a globally important working city.
Its great you can do that, not everyone can code that well but i'd bet they'd have better success at configuring systemd to do that.
"a) I want it to be ASCII "
"b) I don't want to have to replace my init daemon, and I shouldn't have to."
They are both your choices. if your preferred distro uses systemd then you have vote with your feet and move to another distro. The distro have every right in the world to put out the system the way it sees fit and if you don't agree with it then you have to move or suck it up - thats life.
I suspect that if they took rsyslog and updated to make it work the way journald works that would cause just as much shit in the forums so writing their own version would have made sense. There are a few important reasons for developing the journal solution listed here in the section "Background: syslog" https://docs.google.com/docume...
I understand what you are saying but a lot of the startup/kill scripts are basically the same code for starting, stopping and restarting services etc (a lot of duplicated code in many files) so it makes complete sense to launch all the services etc in a rationalised common way but allow for exceptions to the rule.
what a crap analogy. look up the definition of monolithic, redefining it to suit your argument is a crock of shit. Delete all copies/versions of shared libraries from your system and see how well it works, then by your definition the whole of GNU and linux is one big monolith.
"Earth used to be a molten ball of lava and here we are." - i'd be interested to see how long you fare in those conditions if it returned to something close to a molten ball of lava
Slashdot Mirror
only one daemon runs in PID1 according to "System Activity" on my system. try again, ignorant troll
FreeBSD's Jordan Hubbard sees need for a modern init system with features like systemd/launch
http://www.reddit.com/r/linux/...
"A second point is that it is easier to feel comfortable on the system, because the whole thing is consistent and easy to understand, provided you take some time and learn about the concepts." - very true. its the problem that most people moaning about systemd are out of their comfort zone and mostly shouting from ignorance of what systemd is and does.
"many" ??? just a few and as they are generally ACs, they are probably the same person. what are they going to do when FreeBSD implements their own version of systemd?
well, blow me down with a feather, software has bugs, i never knew that. the sky is falling
and a serious admin certainly wouldn't put 7.1 straight on production machines (as you imply they would)
you don't half make things up. the logs produced by systemd are miles more informative than syslog, just learn to use them
Want to buy buy a double layer tin foil hat? you look desperately in need of one
you really are an ignorant troll
yawn....
my god, some people still haven't got the message..... just configure it to use rsyslog
You'd better be quick, FreeBSD has already been talking about creating their own version of systemd
no, its only proprietory OS users that like to steal
yeah, and i wonder just how much tax they will avoid paying
"The notion that BBs competitors should prop up the dying BB platform in some notional sense of fairness is stupid." - are Netflix et al really BB competitors, i would have thought that was Apple, Samsung etc? Anyway he's just saying similar to what others have said about wanting MS Office being able to run natively on other platforms but he is just spouting from another perspective.
Unless the change has unknown effects i.e. making it easier for volcanic eruptions or tectonic plate shifts to cause tsunami like flooding
"The only losers in these scenarios seems to be the rich 1%ers who can afford ocean front property" - as much as i'm with you on that, a lot of the worlds important cities are on the waters edge, losing an importatn city could cause all manner of problems for that country and globally if its a globally important working city.
bollox. if you believe the "monolithic" shit then more fool you
no he isn't, Brian is the messiah...
Nicely put, thanks from all the rational ones.
Its great you can do that, not everyone can code that well but i'd bet they'd have better success at configuring systemd to do that.
"a) I want it to be ASCII "
"b) I don't want to have to replace my init daemon, and I shouldn't have to."
They are both your choices. if your preferred distro uses systemd then you have vote with your feet and move to another distro. The distro have every right in the world to put out the system the way it sees fit and if you don't agree with it then you have to move or suck it up - thats life.
I suspect that if they took rsyslog and updated to make it work the way journald works that would cause just as much shit in the forums so writing their own version would have made sense. There are a few important reasons for developing the journal solution listed here in the section "Background: syslog" https://docs.google.com/docume...
I understand what you are saying but a lot of the startup/kill scripts are basically the same code for starting, stopping and restarting services etc (a lot of duplicated code in many files) so it makes complete sense to launch all the services etc in a rationalised common way but allow for exceptions to the rule.
This should have been picked up in testing.......... looks like they didn;t do much
what a crap analogy. look up the definition of monolithic, redefining it to suit your argument is a crock of shit. Delete all copies/versions of shared libraries from your system and see how well it works, then by your definition the whole of GNU and linux is one big monolith.
"Earth used to be a molten ball of lava and here we are." - i'd be interested to see how long you fare in those conditions if it returned to something close to a molten ball of lava