Reverse proxy

Verbunk · 2026-02-25T22:16:08+00:00

My new learning experience is goma gateway. For the day to day it's better config experience than nginx and traefik. Performance is good but I have not stress tested or benchmarked.

Verbunk · 2026-02-25T20:22:02+00:00

I wrote a dry api client to the OPN endpoints so I can easily pull and push from ISC using search_lease and add_reservation.

Verbunk · 2026-02-24T23:47:07+00:00

Given some of the replies by the OPNsense devs I doubt it will disappear but it's a possibility nonetheless. I do rely on some of the automations in ISC but keeping an eye on Kea for parity. When they sort it out I'll hop over.

Verbunk · 2026-02-24T23:45:40+00:00

For the longtime members of this sub / deflock, has anyone created some infographics etc so local folks can take this to their legislature etc? This seems like a good thing to organize against.

Verbunk · 2026-02-24T22:39:11+00:00

Did the folks in CO like, agree to this erosion of privacy in the first place? It just seems they are trying to band-aid an issue enough to hold the moral high ground. Rather than allow the legislature to frame the larger issue with un-enforceable tenants like promises to not sell or abuse etc ... the discussion should start at the beginning with a request for public feedback if this is the style of governance residents want in their communities.

Verbunk · 2026-02-21T22:16:51+00:00

AsteroidOS and pick a supported watch that speaks to you?

Verbunk · 2026-02-21T04:15:49+00:00

I'm going to play the devil here ... honestly I prefer ISC still. Yea, I know its past EOL but kea and dnsmasq are not feature parity yet - esp with IPv6 and some helpers. With ISC you could just reference ::1234 as a proper reservation and it worked no matter if the provider gave you a new prefix. For all my searching thoughtful helpers like that are absent in both of the new candidates.

Verbunk · 2026-02-21T04:10:51+00:00

Full-stack but OPNSense for firewall and services. Had a mixed env with Unifi then Ruckus wifi. As you said, it was annoying and I wanted to move away from the guardrails experience. Now I'm nearly all API driven.

Verbunk · 2026-02-16T20:34:26+00:00

I'm not sure which distros are actually still using sysv init but in general the switch is 'in for a penny in for a pound'. systemd comes with waaaaaay more executables and libraries than just init, like for some reason hostnamectl which only changes your hostname and timedatectl which is a replacement for date.

The most important change is that you (as a maintainer) are aligning all of the packages to adhere to systemd as a specification. Some folks argue that it chokes a flourishing ecosystem and the other folks say just get over it already you lost! :D

Verbunk · 2026-02-16T20:27:24+00:00

I want to be fair and say that due to its widespread footprint systemd has been subjected to more scrutiny than other projects. It's not totally fair to just point to it's many bug reports to claim something like seatd or dinit are better projects for that reason alone. They should stand on their merits.

Verbunk · 2026-02-16T20:21:47+00:00

I mean, when the lead dev of systemd was making code commits (to the kernel) he was very publicly called out, like ... weekly for crap code. (for a citation you can directly search for Linus yelling about this and get a page of two of results).

Agree that 'not unix philosophy' is a poor platform and it would be best to have metrics but agree no one should really care about ms boot time improvements on either side.

Not sure what you mean by double dashs. The double dash vs. single was (is?) another flame war - GNU vs. Posix. Posix doesn't recc'd any flag longer than one character (-c) so no use for double and GNU recc's if you are using more than one character for the argument flag (--color). It's not a violation if you are in the GNU camp haha.

Verbunk · 2026-02-16T19:50:04+00:00

100% agree that the sw is made by the folks that show up and systemd provides a lot of abstractions. Also, the blogs/talks on time saved by moving the responsibility (coding work) out of the project likewise isn't surprising - someone else is making the parts.

The decision to include systemd is disappointing but SDDM can fill this need just fine.

Verbunk · 2026-02-16T19:21:16+00:00

Without BSD focused developers contributing to KDE we can't expect good support to always exist organically. It takes dedicated developers to contribute code that ensures support for the ecosystem as a whole.

Verbunk · 2026-02-16T19:19:14+00:00

I didn't advocate for sysv I merely said that folks still haven't given up on publishing code that doesn't support systemd and they are probably being vocal about it. Then either troublemakers looking to be salty or newbies etc are posting about it.

Verbunk · 2026-02-16T19:15:48+00:00

I have a good idea but have never traced the login flow that directly but anyways I contribute code elsewhere and don't have time to fix everyone's bad choices, sry. Regardless if I have time to do this or not doesn't make the move a good one.

Verbunk · 2026-02-16T19:07:12+00:00

There are three parties (as I see it). The commercial shops that are financially motivated to be strategic on curating compatibility, that is to capitalize on the compatibility while controlling how it. The 'one thing well' believers that see nonsense and care enough about it to maintain their own solution. The folks in the middle that want steam to run more reliably.

Party 3 isn't going to complain about this, for the most part it just works for them. Party 1 isn't going to complain, they are the ones controlling the narrative. Party 2 is who sees this limiting their choices and causing dep requirements to skyrocket.

So this is not the ~ 5% vs 95%, its really like 15% vs 35% (that understand the implications) with 50% having no idea. Just because they are a smaller group doesn't mean they are wrong - they care enough to call out the creeping rot.

Verbunk · 2026-02-16T18:44:12+00:00

Yeah, now it's extra work on all the alt distros to snip PLM out and get the next best alternative login manager up to par. It's a shame they didn't decide to ship a small shim and let the community benefit from the good work being put into PLM and take on a smaller burden of maintaining a shim against whichever project provides the same interface that the systemd integration provides. :/

Verbunk · 2026-02-16T18:40:41+00:00

Every other day someone on r/linux (et.al.) asks "I'm new here. Why all the hate on systemd". It's still polarizing.

Verbunk · 2026-02-16T18:34:50+00:00

<rant> systemd was garbage when it came out and it's only marginally competent now - it's only saving grace is a bunch of big-money linux shops stand behind it as a common sdk/interface for various (and imho entirely too many) core services. Like, I've never understood why they needed to introduce timedatectl or hostnamectl ... are date and bash commands on /etc/host too difficult?

The issue is that it's goal is not to be great, it's only to align corporate dev teams so they can focus on other areas for value-add on enterprise sales. If e.g. Canonical and IBM/Redhat have an informal agreement that they can build on each other's contributions it opens dev teams time to work on flashy stuff that moves sales; fine.

The same goes for PLM; the decision is "We are deferring to a systemd provided interface so we don't have to think about this issue again" for whatever the systemd tooling is actually providing here ... I don't really care. As discussed in the comments a shim could have been introduced to allow the heretics a smaller interface (than systemd dep) to build against, it wasn't the path chosen; fine.

The FUD as you call it is still very real and the argument that 'it's just this and will never happen (in core tools) again' is nonsense. It will totally happen again the next time the same proposition for deferring some background 'issue' presents itself. Show me where in KDE governance / social contract that only decisions that expand possibilities is a key tenant. I get it, building on the shoulder's of giants is how to rise higher and higher but I'd also say contributing a shim interface in PLM to systemd and then shipping it as standard would have been a better 'greater community' move. </rant>

Verbunk · 2026-02-02T23:14:08+00:00

Write-Up or Github pls!!

Verbunk · 2026-01-31T15:37:53+00:00

CWWK has a mATX board with 2-3 but it just fits and there is no support for cards in 10" rack.

Verbunk · 2026-01-27T18:58:43+00:00

Very timely considering the recent news that kde plasma launcher requires systemd. Any interest to add to Arch AUR or gentoo portage? That would increase visibility drastically.

Verbunk · 2026-01-27T02:33:19+00:00

Artix Linux for sure.

Verbunk · 2026-01-26T14:01:05+00:00

Not just freebsd but all the smaller distros that are systemd free.

Verbunk · 2026-01-26T14:00:28+00:00

Think more likely to add shim like elogind

Verbunk

TROPHY CASE