jollyrogue

Yes, I’m using flatpaks.

Yes, I’m trusting flathub. LOL about people repackaging applications. Wait until they find out the Linux distro they use is a collection of software repackaged by 3rd parties. 😂

Userland hasn’t had any concept of security, so it’s nice people are trying to fix it.

That dachshund is so done with that trip. 😆

Damn, I still don’t have a setup to listen my records. 😕

Q: How do we destroy the ecosystem?

OpenWRT saves settings. It’s what’s in the backup, and that’s what allows the router to return to operation after a power cycle.

Things get can sideways when settings are persisted across updates. There is an option to persist settings, but there are fewer headaches when settings are wiped and restored from backup.

This gets even worse when packages are in play. Packages aren’t reinstalled when the backup is restored, so any packages need to be tracked then reinstalled after an update.

You’re opting to self-manage the router by installing OpenWRT. You are the QA department, and it’s up to you to make sure everything works and any manual changes are made.

In a production setting, no not at all. Updates need to be QA’d before being released, especially network equipment updates, to prevent outages.

The Turris Omnia is OpenWRT based and does auto updates, but the Turris is also $300-$400 dollars.

Installation of OpenWRT from stock depends on the device. Some devices are more involved than others.

Updates are not automatic, and they require planning with some down time. The process is backup settings, update wiping out settings, reapply settings by uploading backup.

I do not install packages. That leads even more horribly complicated updates. I don’t recommend using anything that isn’t in the stock image.

LuCI is serviceable. It’s not pretty, or the most intuitive, but it works.

OPNsense is better if you have the x86 hardware around to run it.

Interesting.

What are the hosting details and contrib guidelines?

And some other random notes…

“Best practices for securing Linux” could probably be dropped. There are enough of those, and the topic could overrun the focus on firewalls. I could see a secure network section, but Linux might be too broad.

What about opening it up to FOSS firewalls and networking in general? The BSDs, Illumos, Haiku, and others could be added. Linux could be the starting point, and the others could be added as people feel like it.

I like pointing out compilers exist, and there is a chapter in “The Pragmatic Programmer” about creating scripts to auto generate code.

Also the Texas and Oklahoma Panhandles.

Wow, 30min is really generous.

I bet that was really nice. 🙂 As someone who takes red eyes, showering when I get there would be preferred.

A mobile home. Don’t worry you’ll be able to rent one from Uber for the night soon enough.

Ugh. Bougie homeless. Just sleep in your car like normal people. 🙄 /s

I do want sleep pods at airports.