xi-

They had a perfectly valid configuration and it uncovered a bug in the Linux kernel. That wouldn't have happened had they ignored the issue and tried again.

Of course, anything necessary to get your production box producing, but a well-engineered server is worth the debugging time.

Thank you and all of the contributors for this, it's basically an essential tool for me when writing common lisp.

Not at all, originally the whole purpose of DragonFly was a test ground for its scheduler. It moved on to being much more though, refactoring the entire source tree and rewriting parts of the system. The whole purpose of DragonFly is DragonFly.

Qt has very good and well-documented Python bindings (PyQt).

Also, QML has bindings for a lot of languages if you're not comfortable with either javascript or C++ for your backend.

>This can be done in a single day.

Only if you're lucky. Most of these exploits probably took weeks to find and analyze properly, it's not like one person found more than one a day. They're found because whole teams are working with the linux kernel at the same time and either happen by them or actively look for them.

You benchmarked a compressed filesystem against uncompressed filesystems and are wondering why the compressed filesystem is slower?