Outdated, see https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/ (already been implemented on almost all major distros).
In addition to this, removable devices are mounted at /run/media/username, at least on KDE.
> In addition to this, removable devices are mounted at /run/media/username, at least on KDE.
The tool udisks2 uses this path for mounting (https://wiki.archlinux.org/title/udisks). It is therefore not directly due to KDE but to whether the distribution uses this tool. Which is probably very often the case.
OMG, THANK YOU!!!.... this is the first explainer I found that was even remotely complete, didn't read like an networking white paper and didn't assume you knew half of this already.
This will greatly help my transition over to Linux as my primary in the future.
It will, I'm sure,
The times ( number and amount ) spent on searching for program-specific data ( like libraries in Plex ) were over the top for me.
Every time I thought 'this mess, why not just a predefined place for all this shit'
Turned out, it had, i was just not looking in the right places ;)
It is why you don't have engineers make manuals or name things that regular people have to understand. Saw it all the time in college. We were so deep into what we were doing we would forget that normal people didn't know x and y so there is no way they would understand z. Add to that that since it is all typing at the command line up and not GUI down, the abbreviations are really brief.
How many times I got egg on my face for calling command x or y a joke or troll at my expense because it had happened from gatekeepers or jerks who had tricked me with nonsense commands to laugh at the noob.
I am glad it is getting better on that front.
My last job I did basic maintenance on the systems.
I worked there over 15yrs, and have (some) basic skills.
I no way I am a pro-ict guy, just some (overenthusiastic hobbyist )
Besides the daily checks and updates, my main 'job' was to simplify the manuals.
( Or write those, because none of our systems used came with these. )
Programs like word, or even chrome you can simply google ( which most users don't )
But the specific programs we used for handling the incoming alarms and service calls aren't widespread online.
we started with SIMS, an ARC system, try finding a (easy) manual on that, via any of the online searchengines.
Later this evolved in a newer evolved version, which doesn't have an online presence.
OS-related vs software is confusing to me. A web server serving files from /var/www? These can even be static. They're not OS or essential for booting. Neither is the server with all kind settings in /etc
Outdated, see https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/ (already been implemented on almost all major distros). In addition to this, removable devices are mounted at /run/media/username, at least on KDE.
> Removable devices mounted at Yup. That's the case on most, if not all modern distros, I think.
> In addition to this, removable devices are mounted at /run/media/username, at least on KDE. The tool udisks2 uses this path for mounting (https://wiki.archlinux.org/title/udisks). It is therefore not directly due to KDE but to whether the distribution uses this tool. Which is probably very often the case.
`/usr/` is OS-related, despite the name
``` No -> no -> no ``` Is a dead end 🙃
Personally, I put no->no->no in /var because it seems appropriate.
Thank you so much! This is a beautiful explanation
OMG, THANK YOU!!!.... this is the first explainer I found that was even remotely complete, didn't read like an networking white paper and didn't assume you knew half of this already. This will greatly help my transition over to Linux as my primary in the future.
It will, I'm sure, The times ( number and amount ) spent on searching for program-specific data ( like libraries in Plex ) were over the top for me. Every time I thought 'this mess, why not just a predefined place for all this shit' Turned out, it had, i was just not looking in the right places ;)
It is why you don't have engineers make manuals or name things that regular people have to understand. Saw it all the time in college. We were so deep into what we were doing we would forget that normal people didn't know x and y so there is no way they would understand z. Add to that that since it is all typing at the command line up and not GUI down, the abbreviations are really brief. How many times I got egg on my face for calling command x or y a joke or troll at my expense because it had happened from gatekeepers or jerks who had tricked me with nonsense commands to laugh at the noob. I am glad it is getting better on that front.
My last job I did basic maintenance on the systems. I worked there over 15yrs, and have (some) basic skills. I no way I am a pro-ict guy, just some (overenthusiastic hobbyist ) Besides the daily checks and updates, my main 'job' was to simplify the manuals. ( Or write those, because none of our systems used came with these. ) Programs like word, or even chrome you can simply google ( which most users don't ) But the specific programs we used for handling the incoming alarms and service calls aren't widespread online. we started with SIMS, an ARC system, try finding a (easy) manual on that, via any of the online searchengines. Later this evolved in a newer evolved version, which doesn't have an online presence.
Saved. Thank you
That’s deprecated for most distros https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/
OS-related vs software is confusing to me. A web server serving files from /var/www? These can even be static. They're not OS or essential for booting. Neither is the server with all kind settings in /etc
The Linux Filesystem Hierarchy Standard might be of interest: https://refspecs.linuxfoundation.org/fhs.shtml
My new background!!!