funny how the platform owner blames my network (and a perceived firewall on my side) when 1) hosts are on the same subnet; 2) they're testing using UDP when the port is TCP; 3) their end hosts have hairy iptables configurations
I'll bet my socks it's their iptables config. Original complaint was "Client can reach backup server, but backup server can't reach client"
Yet another LJ post that's stubbornly stood the test of time. I'm having this exact problem with the Ubuntu MATE I just finished installing yesterday.
fighting systemd-resolved again. I don't want that black box in my network path, so of course I stop/disable it. But now I can't resolve anything.
I've resorted to just putting my nameservers in /etc/resolvconf/resolv.conf.d/base for now while I try to work out the correct way to exorcise this d(a)emon from my system.
I wrote this journal entry over 10 years ago.
I'll note that I STILL have this issue today with sad regularity.
I bought JBL Bluetooth speaker.
The speaker itself is great. But then I went to install their app on my phone and discovered that JBL/Harman have no business writing software.
This thing will just unceremoniously dump me out of the app if I don't give it location persimmon. They won't even tell my why location is necessary, either.
And oh... it's 54MB!
>have like 12 terminals open
>realize I need to start a VPN
>systemd is installed
I think I'd rather just get in the car and drive to work and put the two files on a fucking USB key than have systemd wall all of my terminals to ask for a username and password when I started the VPN manually.
It's shit like this that makes people say "I HATE systemd and take that Lennart voodoo doll... and that, and that, and that!"
And now I need to give my Galaxy S7 root access.
It's just used as a remote control. It does not need Flipboard, Samsung *, and other non-deletable, can't-be-disabled-either pieces of shit running in the background.
It's come to this. All this just for the privilege of running Titanium to freeze stuff.
Quasi-related: I remember when micro USB was new, and people claimed it was proprietary because they've "never seen this kind of connector before"
In one case, they had some room for argument, as WD had made the socket just a little too deep to accept any micro USB cable except the one that shipped with the drive...
Now I'm reminded of the Apple USB extension lead that would ONLY work with the Apple keyboard because they put a bump in the socket.
I chopped that stupid bump out and defiantly used the cable to defeat the similarly proprietary socket on a car radio.
Aside from that bump, it was just an extension cable!
commit comment "edit profile" and-quit
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!
We adhere to an adapted version of the TootCat Code of Conduct and follow the Toot Café list of blocked instances. Ash is the admin and is supported by Fuzzface, Brian!, and Daniel Glus as moderators.
Hosting costs are largely covered by our generous supporters on Patreon – thanks for all the help!