@lanodan @MischievousTomato @a1ba Wasn't isolation by using chroot the main point? It ensues bringing all the dependencies in, but that wasn't the primary objective. Am I wrong?
@lanodan @MischievousTomato @a1ba I agree with you, it is broken. Crappy integration is a major problem — but it is actually what they wanted to achieve with isolation. Static linking is not the same as what *they* wanted to do with flatpak — that's what I was talking about.
@MischievousTomato @a1ba @lanodan That's the price you have to pay for sandboxing/isolation, you can't have it and perfect integration at the same time 🤷
@lanodan @MischievousTomato @a1ba P9 was way ahead its time. I hoped it would gain popularity given its distributed nature when all this "cloud" shit was gaining steam, but no workloads didn't shift from clients, you still have to have a powerful one, they've just used "the cloud" as a justification to steal your data.
@lanodan
And microkernels are of course good! I mean everyone resorted to this "hybrid" shit for performance reasons, but now computers and even smartphones have abundance of computing power and we still don't have microkernel-based OSes as the mainstream.
Weren't there any interesting experiments with L4 or something similar recently? There were some interesting ideas with running L4 on top of linux, but I don't remembner anything viable coming out of it.
Well on linux you basically can't, it's a Unix system.
Namespaces are an afterthought, it's not part of the system design, this is why user namespaces are often a security issue, they weren't there ~10 years ago.
And filesystems overlays also have been pretty much always broken in linux, it's kind of wonderful to see them still being broken after all this time.
(I think it's better on illumos and BSD)
Meanwhile If you look into Plan9 system design, you access almost all APIs via files, making it simple to sandbox and isolate.
And I think more recent systems based on microkernels also do similar things.