Like most people on the Interwebs, I was unable to peacefully drink my morning coffee due to the news that Red Hat is going to be bought by none other than IBM.
Am I worried?
We are nearing the twenty-year anniversary of the Halloween documents, and in this context, I find myself routinely answering the same question: why is Azure so important for Linux and Microsoft? Why is it such a big deal?What’s this EEE that old people keep talking about?
There is a part of writing a Linux BSP that I dread profoundly, and it’s among the most trivial ones. Specifically, I’m talking about that part where you’ve written a new device driver, or modified something in an old one, or you just need to configure it. You’ve added the right incantation in the device tree, you boot, and nothing happens. The module isn’t probed, or your changes are silently ignored.
If you’d have told me five years ago that soon enough I will be able to drop a Cortex M IP in my design, at no price at all, there is a good chance that I would have said something snarky about optimism and how harsh reality actually is.
And yet here we are. Arm just started giving Cortex M IP cores away.
It turns out that the rumours about impending doom are false. I have left my bunker today and it appears that the sky has not yet fallen, and that the world as we know it still exists. And yet, the unthinkable has happened: Linus Torvalds apologized for his behaviour, and has even decided to take time off in order to improve it. And a controversial (?) Code of Conduct has been adopted.
I do not want to defend or attack this decision in this post (although, for the record, I would certainly defend it). What I want to talk about is how the FOSS world has changed in the last fifteen years or so, and why I think this happened.
The Debian project just turned 25, which calls for celebration. Unfortunately, I’m on a pretty restrictive diet at the moment, which means that beer is out of the question. So I settled for the second-best solution: I took Debian 3.0, the first Debian version I used, out for a drive.
USENIX Security may not be the most glamorous security conference today, but I cannot remember the last time I’ve looked over the proceedings and said oh well, nothing interesting happened this year. And USENIX Security ’18 is no exception.
USENIX graciously publishes all the papers presented at the conferences that it organizes, and the proceedings of USENIX Security ’18 were just published. What better to do on a hot August afternoon, right?
There is plenty of interesting reading material in there, but eight papers in particular caught my attention.