zlacker

Bad/illogical/outdated directory structure is one of the most annoying things I've encountered while using Linux, because it makes the admin job feel unnecessarily messy (things are all over the place), and it feels as if there's a fundamental imbalance in the system that you can't get rid of.

>>vfinn+(OP)
There is really not that many places to look. I agree it could be better but part of the time the issue is with package maintainers. And to some extent, systemd has made things a little more convoluted. Compared to Windows it is far better because at least you don't go having to search thousands of registry keys.

>>vfinn+(OP)
>Bad/illogical/outdated directory structure is one of the most annoying things I've encountered while using Linux

Every OS I've ever used has had these kinds of quirks, save simple ones that just dump everything in the root folder or equivalent. Its really hard to move files once you ship software and doubly so do an OS. Users expect files to be where they were last version.

>>vfinn+(OP)
> it makes the admin job feel unnecessarily messy

Many admins feel like a Jedi when they memorize all the trivia about a file's path.

There's no shortage of people in a particular profession that feed on unnecessary complexity even when the original reason for said complexity (i.e. tiny drives) doesn't exist any more.

Now if you'll excuse me I have to figure out why sound doesn't work on Linux in 2022 like it's 1997. No seriously, I legit have to do that now. Someone should really develop another system for sound, again.

>>encryp+9
At least for the PATH, you can also automate the looking. When on a new POSIXy system, I usually try "(IFS=: ; ls $PATH)" at the shell to get a listing of all programs available.

>>li2uR3+gu
"I use arch btw"

>>li2uR3+gu
I just got done building an omni-channeling recording system, with a soc running ubuntu-server & alsa handling recording from several usb dacs connected to microphones. I feel your pain. Sound on linux is a nightmare. But now that I have an understanding of it, here are some helpful things I learned.

- Make sure alsa-utils is installed

- Auto-configure hardware devices: alsactl init

- View hardware for playback (use arecord for opposite): aplay -L | grep “^hw:”

^ Use that to make sure your hw is being detected

- Lower level list of sound cards, if having issues: cat /proc/asound/cards

- Base alsa conf: /usr/share/alsa/alsa.conf

^ go there to dive deeper into what alsa is actually doing. It will also show you the priority for config files, so you can go through that and check which ones are in use and modify accordingly. alsactl init should handle most configuration though.

- you will want to mess with this: /etc/modprobe.d/alsa-base.conf …and get it working for your hardware. This is a resource to understand that file better: https://alsa.opensrc.org/MultipleCards

You can google configuration files and find one that works for you. Most issues for normal use will revolve around which card gets set to index 0 / default, so if you know your card you want as default, I’d recommend finding your device id (i think cat /proc/asound/cards will give you vendor/product ids you can use) then making a config using that id to set it as the default card, independent of indexing.

Turned into a lot, stopping here. Sound really shouldn’t be this hard for end users or devs, but it is what it is right now. Anyway, it’s fresh on my mind so at the very least, I might be able to point you in the right direction.

Good luck!

- Someone with no more hair left to pull out