this post was submitted on 22 Apr 2026
3 points (100.0% liked)

Linux

64839 readers
1170 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

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 7 years ago
MODERATORS
nooter692@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
3
What's the proper way to install every-day CLI tools on immutable distributions like Fedora Bluefin? (lemmy.world)
submitted 2 days ago by versionc@lemmy.world to c/linux@lemmy.ml
26 comments fedilink hide all child comments
 

I've read that containers are preferred for development, but they aren't persistent and it doesn't seem like files such as /etc/fstab can be accessed through them when running distrobox (I enjoy editing such files using vim).

It's also a bit annoying having to enter a specific container to run something like btop.

Are you supposed to layer them with rpm-ostree?

you are viewing a single comment's thread
view the rest of the comments
[–] jokeyrhyme@lemmy.ml 1 points 2 days ago

I switch back and forth between bazzite and bluefin quite often

on these and other immutable distributions, /usr is read-only, and the recommended is to use installation methods that write to your HOME (or to /var which is where docker and flatpak --system save files)

i really should muck about with container-based development flows

my current preference is flatpak, then whatever per-language package tooling (e.g. cargo for tools written in Rust, npm with a custom HOME prefix for tools written in Node.js, uv for Python projects, etc) when there's no flatpak, then homebrew, then rpm-ostree as a last resort

for editing files in /etc my recommendation would be to set the EDITOR environment variable to point at whatever you like, installed however you like, and edit with sudoedit /etc/fstab, because then your editor is not running with root permissions

you could also point EDITOR at a custom script that mounts the target file into a container running your desired editor