5 ms·
I found Silverblue to not be flexible enough for my person computers. Maybe I use Linux in a hacky way, not having write access to /usr or /bin or other folder
by hx8 3y ago
I found Silverblue to not be flexible enough for my person computers. Maybe I use Linux in a hacky way, not having write access to /usr or /bin or other folders drove me crazy about once every two weeks.
For example, I was using a script written by an ubuntu user that was looking for a library with the name/location ubuntu puts it in. Fedora uses a different name for the library. My instinct here is to create a symbolic link with the Ubuntu name that points to the Fedora rpm managed library. Instead, to get it to work I forked the script, got it to build locally, made it look for either library name, ran local test cases, submitted the code as a PR upstream, etc etc etc. It took something that would normally cost me 1 line of shell to fix to something that took 90 minutes.
- anthk 3y agoUse toolbox and do all your CLI scripting there.
- INTPenis 3y agoWow you're using Silverblue all wrong, you're even using regular Fedora wrong. Even before I switched to Silverblue I was known to create Ubuntu containers to run tools from there. That's what you should have done, run it in a container. If you're not comfortable with containers then the workflow in Silverblue will feel very strange.
- yjftsjthsd-h 3y ago> My instinct here is to create a symbolic link with the Ubuntu name that points to the Fedora rpm managed library. I sympathize, but also AIUI this is exactly the sort of monkey patching that these systems are trying hard to avoid; yes, it fixes your immediate problem, but it leaves an undocumented, unmanaged change in how your system finds libraries. In my personal experience, this is the kind of change that leads to machines growing weird behavior that ends when I give up and so a clean reinstall.
- akvadrako 3y agoThere are 3 ways to get what you want more easily: 1. With Fedora Silverblue 39 the most straightforward way is to add a Dockerfile layer just which makes your changes directly to the base image. 2. You can also create your own RPM and make the changes there. 3. Best is to actually run your script in an Ubuntu container (distrobox, toolbx, or podman).
- curt15 3y ago>1. With Fedora Silverblue 39 the most straightforward way is to add a Dockerfile layer just which makes your changes directly to the base image. Does that put the onus on you to rebuild container image in order to receive system updates?
- curt15 3y ago> not having write access to /usr or /bin or other folders drove me crazy about once every two weeks. How do you keep track of your custom modifications to /usr or /bin without using the package manager? Do you record them somewhere for reference?
- nonameiguess 3y agoWouldn't it have been easier in this case to edit the script?
- aeroevan 3y agoOr just run the script in an ubuntu environment in toolbox/distrobox?