Because I wanted to see the partitions such as /, /home/ and /boot and etc except the /dev/loopN file system partitions by the df command. The /dev/loopN partitions made me hard to see these partitions. I was always removing the loop file systems like this.
For me, it is a requirement for running a usable desktop on Fedora. I can’t imagine using Fedora without it. Fedora’s policies on software licensing are unbelievably strict. rpmfusion the easiest way to avoid that issue.
Personally, I use rpmfusion first and flatpak second. They aren’t mutually exclusive.
There often are conflicts in function if the same app is installed from both sites. For sanity and reliability always ensure each package installed is taken from only one source and not installed twice on your system…
Same as above, my preference is: 1) rpmfusion, 2) flatpak.
Typically these are my considerations:
is the application open source, if so, prefer rpmfusion
is it preferred to run the application in an isolated environment? prefer flatpak.
Conditions when that is the case:
it’s proprietary and relies on outdated dependencies (e.g. old version, 32 bit, etc; steam is an example)
I don’t “trust” the code, as in, collects user analytics that cannot be turned off (e.g. Zoom, Teams, Slack, and other applications common in work environments)
am I just trying out an application? I’m 50:50 on that, using flatpak here has the advantage of cleanly undoing an install. A recent example for me was when I wanted to try out different Matrix clients because Elements doesn’t support multiple accounts cleanly.
Things to be aware of:
since flatpak is an isolated environment, it does not have access to all files in $HOME. Typically only xdg-user-dir DOWNLOAD. So for things like sharing a file on Teams, I have to copy the file to my DOWNLOAD directory before I can open it.
your $HOME should have sufficient disk space if you use apps that store a lot of local data. E.g. this is how it is for me on my desktop at home: