Tobu

They have this in beta: https://www.ovh.co.uk/cloud/public-cloud.xml

Their 64bit kernels can run a 32bit distro too. With multiarch you also get to cherry-pick packages of the other arch.

Thoughts on LGPL vs MPL vs GPL with linking exception?

It does look unpromising; even something like nacl_dyncode_copy is too restrictive for the PyPy JIT (can't patch jumps).

The cards have two links that do 10Gbps in each direction. The 16MB buffer will hold 7ms at worst (double if the links are unbalanced and the buffers shared), which might be okay for web content. Frankly CloudFlare should focus on making their ddos filter more realtime and get over their fear of dropped packets.

RED has too many tunables and overfits for a single traffic profile. Fair queuing CoDel just needs a bit more testing to become the Linux default (the current default is a fifo, which is horrible but simple). In addition to that, a lot more work is required to eliminate dark buffers in wireless drivers and other places.

Password reuse is still bad, your password doesn't have to be breached through a database dump. You could be accessing a compromised site, or get caught by any number of network attacks from stripping to mixed scripting to dumping a stream that doesn't have forward secrecy. https://www.imperialviolet.org/2012/07/19/hope9talk.html

Ubuntu is splitting logind from systemd with no help from the systemd maintainers, because some gnome projects have started requiring logind. That effort is spent undoing Lennart's work swallowing most of the consolekit code base into systemd. The systemd maintainers won't accept patches that make logind a separate project again.

(Storage=none is streaming things through the journal, which I have no use for)

Apache2 and Nginx are modular. Let me tell you the story of a small web application.

Once upon a time, requests were hitting an Apache server, dispatched to mod_python, and an embedded interpreter was keeping itself warm running Python code to answer the requests.

As the site grew, and the state of the art evolved, a programmer wrapped the application in a wsgi container, and gave it to a mod_wsgi container so that it would run at its own pace.

One day, the programmer brought home an nginx server it had found freezing in the tundra, and gave it a job serving static content in front of Apache. Nginx brought his uwsgi friend and they took turns running the site, nginx serving images and scripts, uwsgi replacing mod_wsgi.

This is what a competitive space looks like. Apache has competing modules, there are http servers and wsgi servers, some of them embedded, some of them external, http servers can collaborate or replace each other when a better thing comes along.

You don't see an http server deciding it will be the sole http server on the system, swallowing a wsgi server and waging war to all others.

I can't disable the journal, for example. If I run something more full-featured, I'll still be streaming things through the journal.

It's not at all like the kernel does it. With Linux, there are multiple competing implementations of most features, pushed by people with competing interests. There is a lot more room for debate and experimentation.

It's monolithic because you can't pick and choose the components.

You have to use all of systemd, or none of it. You can't replace bits of it, or use just parts of it.

> 1)

Conceded.

> 2) "Now systemd's syslog compat is seen as unnecessary overhead"

I can't believe rsyslog compat won't suffer, well-meaning reassurances from a third-party can't trump the documented attitudes of core developers who aren't bound by them.

> 3) The trend, what you perceive about the slippery slope of things

I've illustrated a lot, I could easily find more.

I do in fact believe Lennart et al are developing and promoting a system (distinct from the Linux ecosystem) that they consider genuinely superior. It's what being an open-source developer is all about. It doesn't mean they aren't engaging in some ends-justifies-the-means politicking on the way to world domination. I'm fed up with the latter, and with having the bad forced with the good.

journald was enabled in Fedora very recently, on the premises that no one would feel a thing, just an implementation detail of systemd. Now systemd's syslog compat is seen as unnecessary overhead, and at some point the goalposts will move again and alternatives to the systemd journal won't be supported.

I'm writing this because I've been seeing the same sort of shifting promises when systemd assimilated udev. At first it was a trivial repository merge, just something to make the developers more comfortable, no impact to anyone else. Now building udev without systemd is unsupported, and some “cleanups” are made to tie udev to systemd and kmod. This doesn't benefit systemd but it hurts anyone who uses an alternative.

The same kind of breakage of alternatives is pushed on gnome via logind, and the kernel via cgroups. It would be myopic to focus on promises made in a particular thread and ignore most of systemd's history.

PyPy reuses the Python stdlib as much as possible (though they do have patched up and/or rpython versions of some modules). PyPy's advantage is performance and hackability, but the stdlib isn't critical to that.

(e)glibc and friends are fairly critical since they are the one exposing kernel features. Those that save a bit of space on embedded systems also have a selling point. For C++, aside from must-haves like open-source licences and community support, I don't see what the differentiators are.

There may be ways to do it right now, but it's hard to fight the fact that Lennart doesn't want it to be supported. He's already thinking of deprecating initramfs builders that don't have systemd running inside (which causes trouble for Arch). If systemd continues to clash with initramfs tools it takes human resources away from working on things Lennart doesn't care about.

I haven't seen it in the discussion, but systemd's journal has horrible read performance. Apparently it's poorly indexed, or the disk layout has issues.

systemd's philosophy seems to be “bundle everything, attack anything we haven't assimilated”. The source is relevant.

He also claimed that he didn't exactly object to paying, but I'll believe it when I see it.

> on pensait d'être le gold chez openstack, mais il y a des obligations qui nous refroidissent

We thought about becoming gold at OpenStack, but there are some obligations that cooled us off

He has another problem with OpenStack; he made this claim:

> @tcarrez on nous a fait clairement comprendre qu'il y a aucun espoir de reprendre nos patchs sur MOVE si c'est pas dans la roadmap/sponsor.

We were clearly made to understand that there was no hope to take our MOVE work if it wasn't in the roadmap/sponsor.

> on veut pas de nos patchs. nos besoins ne sont pas dans la roadmap. il faut payer pour la modifier.

Our patches aren't wanted. Our needs aren't on the roadmap. You have to pay to change it.

Thierry Carrez is the OpenStack release manager, sits on the technical committee, and posted some links on OpenStack's open governance (which don't mention a roadmap; the term may have been used loosely). As long as they keep talking[1], this may still end well for everyone.

[1] https://twitter.com/olesovhcom/status/357881953661353985

Patch and diff mean the same thing in this context, AMHA the original translation is a legitimate clarification. But guy does work better.

> so over the top that it's impossible for them to be completely serious.

You are completely correct: https://www.kernel.org/doc/Documentation/ManagementStyle (ch. 2, but the whole thing is worth reading)

John Cage? You were quoting Gustave Flaubert:

> Pour qu’une chose soit intéressante, il suffit de la regarder longtemps.

http://flaubert.univ-rouen.fr/correspondance/conard/outils/1...

That's an abort(). libmkv encounters an invalid file, throws an exception, vlc exits immediately.

> VLC threatens to sue Secunia over full disclosure

Not full disclosure at all, just security claims that no one can back up.

Secunia does seem selectively clueless (I think of it more as fear-mongering, what with the Twitter posturing and stealth edits of their reports), but AFAIK their vulnerability index exists to be linked from their "software inspector" products which scan binary Windows releases, which do tend to include bundled libraries.

However, their blog post makes no mention of that, and they don't seem to question the link between vulnerability PR and actual, verifiable vulnerabilities.

I like github-backup[1], which I think does something slightly different; it mirrors github issues and the rest of github's non-git metadata.

[1] https://github.com/joeyh/github-backup

Linus is a good, pragmatic designer and a fantastic manager. Do give him some credit for fostering the kernel community.

While they could update the list, it's still typo correction. As implemented, the url needs to be typed in the location bar and the domain can't exist.

Edit: sorry about that last part. http://amazon.co does exist and does get corrected.

Okay. It seems that if I enable the typo feature (which is disabled by default, I've just checked in a clean profile) and go to amazon.comm, I get redirected to http://amazon.com/?tag=uf024-20

ABP notifies me of the redirection, and I can accept or blacklist it.