You want to ship binaries for linux?
Put that in packages, otherwise you're probably going to have some binary-compatibility horror.
@lanodan how do I package without physical and psychological pain?
@lanodan writing only an ebuild doesn't count.

Most people use Arch, Ubuntu or Fedora. And all of them are just purely bad.
@a1ba Guess why I don't use those distros?

If I'm missing a package for anything, it's a nightmare to grab it.
So to me they are failed distros, and I don't see why I should have to bear the pain of other people's choices.
@lanodan @a1ba at least writing a PKGBUILD for arch seems easy, compared to RPMs or DEBs
@MischievousTomato @a1ba Arch is more of a pain because of the absolute instability of the system.
Quite like how with python you need to at least bump your packages every 6 months in most distros.
@lanodan @a1ba :think_happy: i guess. I havent messed with packaging yet. Currently, as just a user who loves the concept of flatpak but still hates how messy it is, arch and its aur work greatly.
@MischievousTomato @a1ba Flatpak is a horrible hack.
Learn static linking if you want to ship blobs that ignore the distro.

@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?

@m0xee @MischievousTomato @a1ba
Flatpak problem is mostly: Yeah, please ship me an entire distro as blob that can't be rebuilt/modified. So in practice, everyone looses the rights guaranteed by FOSS licences.

(Also crappy integration in the host system, meaning broken accessibility)

@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.

@m0xee @lanodan @a1ba > crappy integration is what they wanted to achieve
what the fuck?
Follow

@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 🤷

@m0xee @MischievousTomato @a1ba
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.

@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.

@MischievousTomato @a1ba

@m0xee @lanodan @MischievousTomato

wait for security patches to fix all excessive computing power :)
@m0xee @MischievousTomato @a1ba There is some things to have linux (maybe just binary-compat, linux is the Windows of Unix) on top of L4.
Not sure how good they are, it's so horribly academic hands-in-hands with proprietary software that I had no idea how to use it.

I've seen "Xen microkernel" few times as well but I'm not sure if it's people being wrong or if there is a microkernel-based system capable of being a Xen host somewhere.
Sign in to participate in the conversation
Librem Social

Librem Social is an opt-in public network. Messages are shared under Creative Commons BY-SA 4.0 license terms. Policy.

Stay safe. Please abide by our code of conduct.

(Source code)

image/svg+xml Librem Chat image/svg+xml