Check_mk is not a nagios/icinga fork, it's an addon that works with them. It's a host agent (like NRPE) that bundles all the local checks in a single run and submits them on Nagios as a passive check.
Yes let's cripple the web by continuing to use unencrypted http, just because computers from 15 years ago won't be able to properly display some webpages...
It's not at all strange. Security updates to publicly-facing services should be applied as fast as possible. Kernel vulnerabilities are a whole different attack surface
We use twisted-vncauthproxy[1] to open a noVNC console from the UI to speak with the VNC port that each KVM is running on. Before that we used a Java applet with a similar vnc proxy software.
This is not about bloat. Mozilla was already developing read-it-later functionality for Firefox. In fact it's already on mobile versions. Hello and Pocket have almost no overhead because they are just APi calls to external services. This is about Mozilla endorsing thrid-party proprietary services.
Browsers don't natively handle .flv files, they hand off the file to the flash plugin. If you try that with files the browser can handle (.mp4 videos, .mp3 music, .png images, etc.) you'll see that it works fine.
But Nginx is not running the PHP code, whatever the application daemon on the background does. Nginx simply proxies to it. Apache can get similar performance if you offload PHP and not use the mod_php.
Nop. 2.0.5 here (2.0.8 is the latest) and f works just fine. I guess barrkel had enough time to whine on a forum but not enough to look in the program's preferences.
There's nothing ironic about that. Due to it's open nature (i.e. anyone can manufacture an android device that runs whichever version of the os he likes) there is fragmentations. Just like the different linux distros...
And how do those millions of unemployed people feel about the fact that they probably won't get that call simply because of the incompetency of said recruiters?
Although the different prompt style for remote systems is still handy, cause there's tons of other stuff you can do accidentaly that could cause damage.
This is false.
Not only Tab doesn't automatically send the email but Google has not overwrittern anything. This is the default behaviour on a web page. Pressing Tab selects the next interactive element on a web page (a link, form elemnts etc.) and pressing space/enter activates it.
I'm guessing you press tab expecting to indent something, write a word and then press space to begin the next one which actually sends the message.
This is how forms on a webpage work and AFAIR this is how the compose function in gmail always worked. I think i have seen a couple of WYSIWYG text editors that "capture" the tab keypress and actually ident the text but this is far from the norm.