You, like the NSA, seem to have forgotten that part of the NSA's job is defence. That they knew of these vulnerabilities and didn't work with microsoft to fix them is a failure of that job..
Several experts monitoring the situation have linked the infections to vulnerabilities released by a group known as The Shadow Brokers, which recently claimed to have dumped hacking tools stolen from the NSA.
Here's one: sysvinit is unable to manage services.
You should read the manual page on inittab - that is what it does. It is clear you do not understand what initd is capable of whilst you criticize it.
You are both right. sysvinit is unable to manage services, but initd is. The problem is is that sysvinit is not initd. sysvinit is a festering pile of shell scripts that ignore almost every interesting feature of initd.
It logs whatever you ask it to log. I have seen problems caused by people writing units and/etc/init.d files that specifically asked for no logging to be done, which then gets blamed on systemd.
When systemd was first being developed a lot of the bug reports were around problems with system crashes that resulted in corrupted and unreadable binary logs. They were all closed as WON'T FIX and some basically said "it's your problem."
Since there were many of these bug reports you'll be able to give a link to one of them, right?
By the way, don't bother giving a link to bug 64116 without reading comment #3.
Other stuff that is a major PITA with systemd: OpenVPN. Whenever I change my.conf file I have to update systemd with some whacky config because it 'caches' my config file in it's own little world.
It does? news to me, I've just been setting up openvpn on my new jessie servers and nothing got "cached".
WTF is that about? Dunno but it's enough of a pain that I'll be jumping to the debian boxen to devuan and tossing the ubuntu for the same reason.
Wouldn't it just be easier to install sysvinit if you don't like systemd?
It wasn't so hard to build, though I did manage to break a trace on the circuit board by soldering and resoldering a chip in the wrong place, fixed it by adding a wire.
I even added the hacky graphics card that worked by using the CPU as a 16 bit counter.
Actually it was to some extent based on Ubuntu, given that the init(1) replacement was upstart, but most of the non phone specific packages were from Debian.
My current phone uses Wayland and systemd, just to freak out any passing VUAs.
Slashdot Mirror
You, like the NSA, seem to have forgotten that part of the NSA's job is defence. That they knew of these vulnerabilities and didn't work with microsoft to fix them is a failure of that job..
Right, because competent professionals are infallible, and never make any mistakes.
Anyone who uses Windows in production systems is not a competent professional.
Windows is for playing games, any other use is suicidal.
Several experts monitoring the situation have linked the infections to vulnerabilities released by a group known as The Shadow Brokers, which recently claimed to have dumped hacking tools stolen from the NSA.
So you're making shit up like I thought.
Bye.
As for put up or shut up - don't take it from a biased person like me just look up the bug reports.
Which bug reports?
What are the missing features?
What has not been logged that should have been logged?
Why?
Be concrete. Put up or shut up.
The fact that most of the systemd proponents seem to inconveniently ignore that nobody likes to be sodomized
Nobody? You need to get out more.
The problem is that you cannot fully get rid of systemd in Debian.
Go, on, tell us what you can't get rid of. We all like a laugh.
Wasn't Open/Free/whatever software about choice ?
To some extent. That's why Debian, unlike Devuan, gives you a choice in what init system you use.
Don't like systemd? Don't use it.
Why does the conversation continue beyond that point?
I feel like most of the complaints against systemd are little more than graybeards complaining that something is different.
Very few of those complaining have grey beards. Jaromil, for one, doesn't.
Here's one: sysvinit is unable to manage services.
You should read the manual page on inittab - that is what it does. It is clear you do not understand what initd is capable of whilst you criticize it.
You are both right. sysvinit is unable to manage services, but initd is. The problem is is that sysvinit is not initd. sysvinit is a festering pile of shell scripts that ignore almost every interesting feature of initd.
service httpd restart
systemctl --restart httpd
that's annoying.
It's also wrong. The systemd command would be
systemctl restart httpd
Of course you could also just do
service httpd restart
and it would work as before.
systemd is Roko's Basilisk.
Heh. Somebody modded you troll. Boy, are they in for a surprise.
Who wrote this incredibly unprofessional shit?
Someone with a sense of humour?
It's still very patchy in what it logs
It logs whatever you ask it to log. I have seen problems caused by people writing units and /etc/init.d files that specifically asked for no logging to be done, which then gets blamed on systemd.
trying to find out why something is not running and the logs not telling me if it's running or not.
What does
systemctl status service
show? Why would you look in the journal to see if something is running?
Keep in mind it's taken a few years to have a mainstream-ish, .deb based distro without systemd.
Nonsense. You can't get more mainstream-ish than Debian and Debian is a systemd-free distro if you want it to be.
When systemd was first being developed a lot of the bug reports were around problems with system crashes that resulted in corrupted and unreadable binary logs. They were all closed as WON'T FIX and some basically said "it's your problem."
Since there were many of these bug reports you'll be able to give a link to one of them, right?
By the way, don't bother giving a link to bug 64116 without reading comment #3.
Other stuff that is a major PITA with systemd: OpenVPN. Whenever I change my .conf file I have to update systemd with some whacky config because it 'caches' my config file in it's own little world.
It does? news to me, I've just been setting up openvpn on my new jessie servers and nothing got "cached".
WTF is that about? Dunno but it's enough of a pain that I'll be jumping to the debian boxen to devuan and tossing the ubuntu for the same reason.
Wouldn't it just be easier to install sysvinit if you don't like systemd?
The messages that say "troll to stupid to invent his own lies".
Va te faire foutre, petit con.
systemd in Debian Jessie makes it hard to recover from a boot problem, so I'm going to look at Devuan.
If you think the problem is with systemd why not just install sysv-init or upstart? What more do you think Devuan will get you?
As does Debian. Which makes you wonder why Devuan exists.
It wasn't so hard to build, though I did manage to break a trace on the circuit board by soldering and resoldering a chip in the wrong place, fixed it by adding a wire.
I even added the hacky graphics card that worked by using the CPU as a 16 bit counter.
Actually it was to some extent based on Ubuntu, given that the init(1) replacement was upstart, but most of the non phone specific packages were from Debian.
My current phone uses Wayland and systemd, just to freak out any passing VUAs.