a tool that allows you to build packages for multiple systems in multiple formats (deb, rpm, nix, flatpak, snap, etc.).

Given flatpaks and snaps are toxic, the other ones - deb, rpm, pkg - can be packaged relatively easily. It’s all a separate effort with files and meta-info that doesn’t often intersect, but it’s manageable. It lends itself incredibly well to the trivial ‘automation’ that gitlab, forgejo and other major git suites provide.

Source: did this for the entirety I built and maintained a software suite for linux and unix,m for like 15 years. I built some code, I packaged it. Because anything less isn’t really ISO27002.

TL;DR - the ‘tool’ is a simple script and your brain. It’s easy work once you overcome the fear of the unknown and start doing it.

1. find something Lennart built. Eg. systemd
2. remove that
3. go to 1

A LOT of plugins in many projects are a huge concern. I say this as someone who ran security for an OS for a while. It’s just people making bad decisions for everyone and then hand-waving the risks when questioned.

till

\sigh

I thought it was naive as well, but because they based it on a mayfly distro that has really great validation and reliability but it’s gone in a fortnight.

Wither Almalinix or Cloudlinux or PCLinuxOS or Mandriva? Three of them have really solid support structures and at least one of them has amazing compatibility options with libraries for services.

There are options. A few of them could be better than fedora while fedora is still owned by redhat as redhat dies from suffocation – hell, its all just fucking ancillary bull (Ansible) they sell now, as its metastatic cancer (Systemd) eats it alive.

Having seen SuSE destroy collaborators like OL, CNC and probably Turbo, I’m okay never even working with them as a customer. I intend to avoid them until death.

Kerberos, you say? Single sign-on?

Have you heard about the LDAP and Kerberos configured as part of setting up samba4ad?

I accidentally enabled SSO SSH a few years back. My samba units aren’t on PIs but they could be. They’re just on tiny tiny VMs.

Facebook made one. They attached a gorgeous voice-controlled video-chat-on-tv setup to it, and released it just as they lost all consumer trust.

Then they decided it wasn’t selling.

So they killed it instead of open-sourcing it

just saying.

Linux (Flatpak)

So, no, then.

Isn’t the video the jingle part that Google added to jabber originally (before it dumped everything to remake it from the group up about 4 more times like a GSoC crossed over with groundhogDay)?

There’s no text chat in mumble? Really? (I seem to remember otherwise, sorry)

Wow, what a wall of text. I’m sorry but I’m sure I skimmed some parts.

Look. The bulk of the replies you’re going to get will be like “this is my favourite distro and here’s how it works for you” not “this is the best distro for your criteria.” It’s important to understand the deep level of bias you’re going to get.

But your cause is a noble one. I use a particular style of distro because it can be trusted to install well, back out well, do both safely, and allow validation at every stage. I think it’s a good candidate, and it’s already been mentioned as a really great ‘set it and forget it’ distro.

Good luck.

The only thing they offer is bare source?

I like they’ve just given up on trying to understand things like filesystem layouts and fucking systemd - which is cool - but now they own dependency hell and inconsistent installs in trade.

Nah. I’ll get a package where I can confirm the contents, check the sigs, reproduce the build and then deploy it with its dependencies in a reliable, verifiably-consistent process.

https://rhel.pkgs.org/9/epel-x86_64/tor-0.4.8.14-1.el9.x86_64.rpm.html

Sources, sigs, signed BoM. Wheeee!

Yum-cron is the way.

Maybe immich will see the way.

Colour + noun:

• redbug
• bluecar
• yellowboat

opensource

Still two words.