4 ms·

It's probably par for the course. Networking is an area that's always felt like shifting ground. Anytime I need to spin up a machine with WoL or (rarely) need t

It's probably par for the course. Networking is an area that's always felt like shifting ground. Anytime I need to spin up a machine with WoL or (rarely) need to edit something at the conf level, it's always a software archeology project, trying to figure out what the new hotness is, where the system vs user config is under the new networking package, grokking the new config syntax/options, and what supercedes if/when multiple networking packages exist on the same host. Knowing the reality, looking at the domain name, given the title, and that it starts off: > It is time to revisit of the simple wifi setup as much has changed [in a year] I am led to believe this is satire.

8jef 3y ago
> I am led to believe this is satire. Looking at their other posts, some very serious not funny at all kind of satire.
raffraffraff 3y ago
This actually reminds me of sound on Linux too. I'm running a bleeding edge Tumbleweed on my laptop and Home Cinema. I now have to occasionally tweak ALSA, PulseAudio and PipeWire stuff. I know that by installing pipewire-pulse, I'm actually using PipeWire, but since it still relies on a heap of PulseAudio conf files and command line utilities, it feels like they've added one more thing to be confused about rather than simplifying the setup. Just try to figure out how to upmix stereo to 5.1 with an LFE channel to your subwoofer. Do you use the (now renamed) lfe options in pulse daemon.conf, some pipewire conf, or the extremely arcane ALSA ttable mappings? There has never been a decent GUI for handling audio in Linux. Sometimes I wonder if I should also install Jack to see if that complicates it more or simplifies it.