That is definitely a sacrifice being made here I agree with you. It gives developers more control over exactly how their app runs, but it does mean less storage efficiency.
This is a secondary account that sees the most usage. My first account is listed below. The main will have a list of all the accounts that I use.
Personal website:
That is definitely a sacrifice being made here I agree with you. It gives developers more control over exactly how their app runs, but it does mean less storage efficiency.
I don’t think Flatpak is going to be compatible with Steam anyway in the long-term because layering container solutions doesn’t generally work very well, and Steam is going to want to use its own solution for better control over the libraries each game uses. Earlier versions used library redirection and some still do.
But y tho?
Are there any conditions about what I can wear under the sweater? Otherwise, it doesn’t seem terrible.
I love what Flatpak is doing for Linux desktop. Let it grow!
I do best at 1 Atm.
Tiny Core Linux is a minimal Linux kernel based operating system focusing on providing a base system using BusyBox and FLTK. It was developed by Robert Shingledecker, who was previously the lead developer of Damn Small Linux.
Ah, that explains a lot! Didn’t know about TCL.
Hm? Do you mean a link to builds that are this small? My midrange Intel i5-12600K (I’m a working man, doc…) L3 cache is 20,971,520 bytes. My Linux Mint (basically Ubuntu kernel) vmlinuz
right now is only 14,952,840 bytes. Sure, that’s a compressed kernel image not uncompressed, but consider this is a generic kernel built to run most desktops applications very comfortably and with wide hardware support. It’s not too hard to imagine fitting an uncompressed kernel into the same amount of space. Does that help to show they’re roughly on the same order of magnitude?
Ten years old kernels could be 2 MB.
I’ve seen builds of the Linux kernel that comfortably fits in my on-die CPU caches.
So it would just be a picture of an empty sofa.
That awful magsafe adapter design with no strain relief grinds my gears.
Are you telling me IP wasn’t intended to be an eternal monopoly?
This is really cool. And is this more or less true to color? Great eye!
As far as I am aware, only the living have a problem with the grave robbing.
It even kills threads currently executing a system call! The brutality!
Never even returned to userspace…
killall
works great for this.
There’s always someone who will look at your life telling you you’re doing everything wrong. And you know what? That’s fine. It really doesn’t matter.
To me it sounds like your root cause is either a driver problem or your hardware is misbehaving a little bit in a way the driver doesn’t expect, firing a lot of interrupts that shouldn’t normally happen.
If this seems to resolve your issue, I wouldn’t lose any sleep over it. I would think my hardware is a little bit weird or there’s a bug somewhere in the driver for it. You can also try different kernel versions if your distribution gives you the option, because kernels come with different versions of drivers.
You can’t kill that because it’s a kernel thread. They are not like normal process; these objects are part of the operating system and terminating such a thread can cause in stability.
It says it’s available for both Intel and Arm architectures. However, I don’t know how well that actually works for both of them in practice.
Different goals and different designs. Why are there so many Linux distro?
Snap is proprietary. Appimage does not include distribution and updates. It also doesn’t attempt sandboxing of any kind.
On the other hand, I find appimage very convenient to use.