296
Did we kill Linux's killer feature?
(self.linux)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 17 Sep 2023
296 points (81.8% liked)
Linux
48300 readers
646 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
Depends. Unless you're on Ubuntu or Elementary, Flatpak and Snap are optional. When I'm on Arch, btw, I don't bother with any of those and just use the AUR with a helper like yay.
But I find the convenience of Flathub too good to pass up on other distros. I have been using Linux long enough to remember when the only options if your distro didn't ship something were to compile from source or to use a sketchy installer script, because Flatpak didn't exist. And as others mentioned, if you're using a full desktop environment, it likely can update everything at once via the GUI.
Normally I do that too but recently wanted to install an app from AUR that ran out of memory during compile on 4 GB of RAM. So being able to use an appimage or flatpak was still useful.
You could have just added a swap file
And I would die of old age waiting for the compile to finish.
Swap is not "disk RAM". It's used for storing pages that go unused for extended periods of time. It's an optimization system designed to be used during normal system operations.
Technically it could solve some mild out-of-memory situations if given enough time but in practice the disk access is so slow compared to RAM that for all intents and purposes your system appears to freeze so you get bored eventually and reboot it. An attempt to compile a large application under these circumstances would last a very long time indeed.
If anything, you should disable swap in such a situation. Without swap the compile process would crash instantly when growing out of memory, with swap your system freezes.
Swap space is also used for storing a compressed dump of RAM during hybernation but that's a special case.
There are lots of options. You can also setup a swap file in memory that uses compression. Since swap tends to compress really well, you can allocate more memory than you have RAM and still not use slower swap on a HDD or SSD.
Yeah, I know how swap works. I'm lazy and it would accomplish the task if needed, I've done it many times before in similar situations especially on low RAM Gentoo machines.
Agreed, it's slow as fuck. It also gets the job done without going outside the package manager.