the various embedded build systems make cross-compiling easy at scale, which means you often don't need to think about it when adding a new package
4,425 karma · joined June 8, 2010
the various embedded build systems make cross-compiling easy at scale, which means you often don't need to think about it when adding a new package
It's probably just garden variety disrespectful behaviour.
Purposeless agent spam won't be cheap entertainment forever, but you're right that later stages of industrialised abuse will be scary and unpleasant.
An example of improving efficiency: virtiofs has a relatively recent feature to map pages from host memory directly into guest memory, but that's a lot of risky acrobatics if your priorities are reliability and isolation...
... but it's not supported by Virtualization Framework's built-in virtiofs "folder sharing". (sad face)
... but someone could build it on top of the new macos 27+ custom virtio device support. (intrigued face)
My suggestion: Don't use the host filesystem from the guest at all. It'll be faster, and better isolated. It's a false convenience.
Depending on your threat model, that's fine, but a lot of people (including me) will say that containers are not a security mechanism.
But macOS requires[1] virtualisation for containers anyway; the security is just a bonus.
[1] at least for a real Linux kernel...
https://www.macrumors.com/2026/06/08/wwdc-2026-live-coverage...
A few things contributed to its demise: less industry money sloshing around for travel and sponsorships, a growing sense that "Linux" didn't represent the entire community, and a pandemic.
Which left "Everything Open" launching weaker in every sense.
But I don't think Linux or Open Source feel sufficiently radical or inspiring to sustain that kind of community-building (local or global) these days... maybe a "Fuck AI" tech conference. :-D
It was Japanese, naturally.
At linux.conf.au 2007 we chose a smaller conference bag, designed to carry your electrical accessories and nick-knacks... it turned out to be the perfect size for the new EeePC (and later the MacBook Air 11").
[1] generally 24fps because that is culturally what film looks like and people get very weird whenever anyone tries to fuck with it
> I must apologise that I haven’t so far open-sourced any part of this that I don’t have to.
With some blather about commercial opportunities. Which is a weird thing to say without linking to the bits that must be shared (under the terms of the various licenses).
Banking and finance companies honour foreign government sanctions. Ask Francesca Albanese.
Libertarian comparisons of government and non-government behaviour always devolves into angel counting.
A year or two before I was born, James Burke wandered between mainframes and reel-to-reel tape machines, speaking with extraordinary prescience about data, communications, decision-making systems, and power:
"This is the future. Because if you tell a computer everything you know about something, it will juggle the mix, and come up with a prediction. Do this, and you'll get that. And if you have information and a computer, you too can look into the future. And that is power. Commercial power, political power, power to change things."
I'm going to watch that scene again, because it's even more important 20 years further along: smart phones, "big data", large language models, Palantir...
... uh?
A bunch of folks decided to get off their butts and gather donations to support Linux... and then it snowballed. Cool. The creators and members get to decide how they contribute, and projects get to decide if they want to participate. There are alternatives for projects that need to "raise and spend", and some are 501(c)(3).
(Also keep in mind that techrights.org has been an unhinged shit sheet attacking individuals and companies for insufficient purity for decades now.)