This sort of thing is exactly what makes forced automatic updates a good idea.

Whoever set up these email servers should have also configured unattended updates and periodic reboots. And perhaps some automated email when the base operating system reaches the end of support. Or simply shut down. Assume it is Ubuntu 16.04 LTS for example. After 2021 it should just refuse to run services.

Because it seems obvious from stories like this that too many people don't know how to maintain technology. The only thing that gets their attention is a boot to the head.

That says a lot more about you than it does about systemd.

ISPs have broken the Internet, which is why new protocols don't work well. They buy crap middleware boxes which only understand IPv4 UDP and TCP, or worse, only HTTP.

In the name of "security" they reject anything they don't understand. And since ISPs are cheap they never update these pieces of junk if they can help it.

And then there's NAT which has to understand the protocol so it can rewrite it.

Since no one can effectively use a new protocol on the Internet, there's no users, so they can point out that there's no demand for new protocols, so there's no need to pay for new hardware or software updates.

The future is what Google's doing with QUIC: encrypt everything and don't give the ISP jerks any chance whatever of screwing with it.

Depends on how you defne "know", but all of these I can get going in and look things up as I need them.

I'm really good with C, C++, Go and Perl.
Decent with Python, Ruby, Bourne shell, C#, Javascript
Forgotten a lot but it'll come back: Java, Scala, Visual Basic, LISP (elisp really).
Still learning: Rust, D, Haskell, F#

Once you've learned procedural, object oriented, and functional styles a particular language is just details. And build tools and libraries and debuggers and analyzers, the whole ecosystem around each one.

Or how you define "language." Does stuff like Make, Ninja, CMake, Autotools, Ant, Maven, Gradle, Cargo, NPM, even count? Or SQL, HTML, CSS? Git, Valgrind, perf, GDB, LLDB? They're almost small languages with all their options and scripting.

Most "middle boxes" won't forward unknown protocols. They're too paranoid about security. Sure, they're willing to transmit absolutely anything over port 443. But an unknown IP type might be a HACKER! Oh noes!

Not only that, lots of them break unknown TCP options. Or TCP windows. I remember years when TCP ECN and window sizes wouldn't work on random internet sites because of their short-sighted, STUPID firewall boxes.

That's why QUIC is completely encrypted. Random hardware and software providers have proven they don't know what they're doing. So don't let them see into the protocol at all. They would only break it.

In actually poor countries with actual poor people, some of them don't have tax-funded mass transportation at all. And yet they manage to do it as private enterprise and make money doing it.

Some guy buys an old truck, fixes it up, drives it around the city with people hanging off the sides while his cousin collects fees or kicks them off the truck.

This doesn't require air conditioning, union drivers and union maintenance technicians. All it needs is free enterprise and an appalling lack of safety regulations.

Even with congestion this is still better than trying to find a taxi or waiting for a bus.

Maybe if mass transit systems weren't so terrible, more people would use them. Cities should try being competitive and offer a better service for once.

Because AMD is careful not to cross privilege levels but Spectre attacks are user mode to user mode. So even though they may be two different users they are still in Ring 3. Spectre can only be used against kernel code if the kernel is convinced to run a user's code for some reason. Like an eBPF byte-code, for example.

But it can work really well for a sandboxed program to steal information from outside the sandbox.

So AMD is still vulnerable to speculation attacks.

I can't convince anyone without a copy of Microsoft's Edge revision control. So I guess think whatever you like.

But if they didn't create a new revision history, then yes it is the same browser. Firefox is still Firefox even though there's nothing left of the original. Linux is still Linux. I think there was an old bit of TTY code and some floppy driver code in the latest Linux left from 1993, but all the rest of it changed, and it's still the same thing.

And as far as I know, Edge was not a rewrite, it was IE with everything old and legacy ripped out.

By replacing small pieces of Firefox with new pieces that use Rust, they are avoiding the Netscape problem. They aren't rewriting the whole thing. But one day the whole browser will be Rust, replaced a piece at a time.

You don't think Microsoft Edge still uses pieces of Spyglass or Mosaic do you? And yet, at no point did they rewrite the whole thing.

They had this in 2005. It was called DPI. It scaled really well. Then some IDIOTS decided it should be force set to 92.

/vmlinux and /dev/mem are just wasting space. I deleted them and nothing bad happened. . .

I've come to the conclusion that there's only about 500 Linux desktop users in the WORLD who have PulseAudio problems. They're all the same people posting on forums about it.

Every other Linux desktop user uses the distro default which is usually PulseAudio, and it works.

This is how I understand it.

Once Firefox e10s (Electrolysis) with sandboxing is enabled by default, every Firefox content process will be independent and restricted.

Most ALSA devices cannot handle multiple open. And the ALSA solution, dmix, requires shared memory which is a thing sandboxes do not really want to have, and dmix does not understand sandboxes, so it would probably have to be forked and modified.

So Firefox can write their own sound server to get sound data from each independent content tab, or blow huge holes in the sandboxes for ALSA dmix, or they can just use the sound server that already exists and is used by 98% of Linux desktop users: PulseAudio.