Distro flame wars and "systemd ate my pony" exists mostly on Slashdot only. I've worked in many 100% Linux places and none of that have ever been an issue.
I'm not so sure, considering the huge amount of poor people living in India I'm quite sure that you can find loads of people who have no clue what Microsoft or Windows is.
Some are yes, other are complex turing complete and others follow the INI style. Look i.e at/etc/openal/alsoft.conf,/etc/subversion/config,/etc/couchdb/local.ini, or why not any of the.desktop files in/usr/share/applications/.
INI style are not bad just because MS happened to use them a lot in MS-DOS, AFAIK there isn't even anything that points to MS being the inventors of the format, just that they used them system until they came up with their horrid registry.
Which opens you up for endless blackmail. #1 install ransomware. #2 collect ransom-money. #3 blackmail victim that you will tell the authorities that they did pay your ransom. #4 profit for ever.
From TFA they installed the servers 8 years ago and have not applied a single patch since. I would say that they already proved to be stupid there and then.
That would just make matters worse. If you criminalize the victims you just make them less likely to involve the police and the criminals can operate far easier without risking getting caught (if no one files any charges then no one will be chasing them and the victims want's their data back).
For one it would make the muggers jobs easier since the victims would incriminate themselves if they reported the crime so basically home run for the muggers!
Please list any democratic country where it's illegal to pay a ransom. Paying a ransom is not equated with supporting a illegal organisation or as fencing in any jurisdiction that I'm aware of. Any attempt to make such payments would only yield one end result; the victims would be extremely less motivated to involve the police.
Must be lots of tests:), I've noticed that autoconf is slow as a turtle on Windows but I have always thought that to be due to the MinGW filename mangling.
There's a difference between a drop-in replacement and a replacement. All the new init systems like systemd, upstart and smf are event driven, and are so for a good reason. The old sysv system was completely hit and miss when it came to exit codes so all those posts complaining that they puppet scripts no longer work had problems on sysv as well. And if you think about it any daemon can die at any time after launch so you must have some other way of checking the status of them anyway (if systemctl return with an exit code of 0 and the daemon failed it's because the daemon failed after it told systemctl that it was up and running).
Because no one wants to have that long command names on Unix? All the new init systems like systemd, upstart and smf are event driven. With sysv as I said you only have hit and miss and people using the exit code from the sysv scripts have just been lucky that it's worked somewhat for them combined with the fact that some of the old sysv scripts contained pre flight checks that the people who ported them to systemd unit files forgot to add.
What exactly is it that people find so horrible with automake+autoconf? The Makefile they produce is completely horrible to look at but the configure.ac, Makefile.am and.in files are actually (IMHO) quite straight forward and they have very good docs at i.e https://www.gnu.org/savannah-c...
Just ignore the fact that it was fixed on Mar 27, 3 days before that Poettering quote. Yes he was wrong, I never said that he was infallible. That people still bring this issue up as "systemd is bad" is part of the crybullying yes, or are we now pretending that "rm" is completely fucked up because it once had the same bug (Poetterings fault was of course that he believed that rm still had that particular bug)? I don't think so.
Read all the posts from AC:s regarding systemd to this article and tell me how you can come to a different conclusion. There are tons of "Poettering don't know about exit codes", "systemd eats logs" and so forth. None of them are true and all of them are crybullying.
No, but it means long term for the upstream Linux kernel. But you don't use that, you use the kernel supplied by your distribution where long term is something completely different.
Please provide the contents of "/usr/lib/systemd/system/mongod.service" either by cat "/usr/lib/systemd/system/mongod.service" or "systemctl cat mongod.service".
Slashdot Mirror
Distro flame wars and "systemd ate my pony" exists mostly on Slashdot only. I've worked in many 100% Linux places and none of that have ever been an issue.
For some reason these scammers have always claimed to be calling from Windows here in Scandinavia.
I'm not so sure, considering the huge amount of poor people living in India I'm quite sure that you can find loads of people who have no clue what Microsoft or Windows is.
I guess you only use global variables as well.
If AIX would destroy the universe as we know it if there ever was a single INI style file stored on it then it would have done so decades ago.
Some are yes, other are complex turing complete and others follow the INI style. Look i.e at /etc/openal/alsoft.conf, /etc/subversion/config, /etc/couchdb/local.ini, or why not any of the .desktop files in /usr/share/applications/.
INI style are not bad just because MS happened to use them a lot in MS-DOS, AFAIK there isn't even anything that points to MS being the inventors of the format, just that they used them system until they came up with their horrid registry.
Because let's pretend that INI files have not been in wide use on Unix for decades?
It uses the exact same exploit as WannaCry so you don't have to do anything besides not having a patched version of Windows.
And you think the fine will remain at 5% if they refuse to abide by the law for long?
Which opens you up for endless blackmail. #1 install ransomware. #2 collect ransom-money. #3 blackmail victim that you will tell the authorities that they did pay your ransom. #4 profit for ever.
Seams to be only because it's about teh terrorists (which of course still makes your claim valid)
Of course both UK and US would go completely bananas when it comes to terrorists, don't know why I didn't see that one coming.
From TFA they installed the servers 8 years ago and have not applied a single patch since. I would say that they already proved to be stupid there and then.
That would just make matters worse. If you criminalize the victims you just make them less likely to involve the police and the criminals can operate far easier without risking getting caught (if no one files any charges then no one will be chasing them and the victims want's their data back).
For one it would make the muggers jobs easier since the victims would incriminate themselves if they reported the crime so basically home run for the muggers!
Please list any democratic country where it's illegal to pay a ransom. Paying a ransom is not equated with supporting a illegal organisation or as fencing in any jurisdiction that I'm aware of. Any attempt to make such payments would only yield one end result; the victims would be extremely less motivated to involve the police.
Well, you now have an idea for a new Kickstarter!
Must be lots of tests :), I've noticed that autoconf is slow as a turtle on Windows but I have always thought that to be due to the MinGW filename mangling.
There's a difference between a drop-in replacement and a replacement. All the new init systems like systemd, upstart and smf are event driven, and are so for a good reason. The old sysv system was completely hit and miss when it came to exit codes so all those posts complaining that they puppet scripts no longer work had problems on sysv as well. And if you think about it any daemon can die at any time after launch so you must have some other way of checking the status of them anyway (if systemctl return with an exit code of 0 and the daemon failed it's because the daemon failed after it told systemctl that it was up and running).
Because no one wants to have that long command names on Unix? All the new init systems like systemd, upstart and smf are event driven. With sysv as I said you only have hit and miss and people using the exit code from the sysv scripts have just been lucky that it's worked somewhat for them combined with the fact that some of the old sysv scripts contained pre flight checks that the people who ported them to systemd unit files forgot to add.
What exactly is it that people find so horrible with automake+autoconf? The Makefile they produce is completely horrible to look at but the configure.ac, Makefile.am and .in files are actually (IMHO) quite straight forward and they have very good docs at i.e https://www.gnu.org/savannah-c...
Just ignore the fact that it was fixed on Mar 27, 3 days before that Poettering quote. Yes he was wrong, I never said that he was infallible. That people still bring this issue up as "systemd is bad" is part of the crybullying yes, or are we now pretending that "rm" is completely fucked up because it once had the same bug (Poetterings fault was of course that he believed that rm still had that particular bug)? I don't think so.
Read all the posts from AC:s regarding systemd to this article and tell me how you can come to a different conclusion. There are tons of "Poettering don't know about exit codes", "systemd eats logs" and so forth. None of them are true and all of them are crybullying.
No, but it means long term for the upstream Linux kernel. But you don't use that, you use the kernel supplied by your distribution where long term is something completely different.
Please provide the contents of "/usr/lib/systemd/system/mongod.service" either by cat "/usr/lib/systemd/system/mongod.service" or "systemctl cat mongod.service".