Interesting. TIL. Thank you.

I did discover this collection of tools that appears to provide code signing by the Linux Foundation project:

https://www.sigstore.dev/

Why can’t RustDesk use Let’s Encrypt instead?

For a time it was Solitaire, but these days it’s 2048.

?

Why type uptime when w is sufficient?

I’ve heard it as:

When’s your Dentist appointment?

2:30.

Wow, that’s some serious misinformation.

And precisely how will you achieve the minimum standard of sustaining human life … trivial things like food and lodging?

That’s very interesting.

A little while ago we tested a bunch of radios for their spurious emissions. Until this post I was unaware that these radios were not tested by the FCC and that it appears that this is also true for other amateur transceivers.

For your information, here’s our report: https://github.com/vk6flab/rhp

I’m guessing that if you set your DNS to AdGuard a lot of this nonsense would go away.

Another alternative is to remove the internet access from your fridge.

More likely than not you’re confusing modifier keys.

On the Mac, the zoom is [Command] + [+].

In Linux it’s [Control] + [+]

This is pretty much true across the board. It’s sometimes non-obvious because wrappers like UTM try to “help”.

The alternative is to ssh into the VM and continue to use the MacOS shortcuts you’re used to.

Source: I’ve been using Linux on MacOS guests for a very long time.

It’s dinner time and why haven’t you fed me yet?

I’m clearly starving, why haven’t you fed me yet?

I’m not kidding around, why haven’t you fed me yet?

Nothing says “I don’t care about my data.” more than the examples in the screenshot.

What happens when two different files in different directions have the same name?

Likely generated spam content, it’s pretty rife. Clear your Watch History and it will likely stop recommending these to you.

Have a look at the modlog.

Fair question.

What it boils down to is: Become part of the OSS community.

In my experience, there’s no other way, since the alternative is to be automatically part of the Microsoft (or Apple) community.

In other words, you need to make the investment into the implementation. As I’ve said elsewhere, license costs are insignificant.

The community is where you get help, where you find others with the same issues. You can pay the likes of Canonical and Redhat, but I’ve never been impressed by either.

Ultimately any solution requires support, just like any other tool. You just need to make it explicit, rather than assumed.

One thing that Microsoft does to ensure that you have support infrastructure is to continually break backwards compatibility in subtle ways that require you to open your wallet and pay for support.

OSS will likely run for years without adult supervision, but that doesn’t mean it can continue to work without requiring support from time to time. If you don’t prepare for this, you’re going to be very unhappy.

Kali ≠ Debian

I did not see an apt-get update

In my experience, unmet dependencies are unlikely to happen on a stable version where you only installed from the official repo.

The LZMA decompression errors point at a much more fundamental issue. I’m suspecting that the repository URLs point at non standard locations or downloads were interrupted, though I’m not sure exactly how, since AFAIK, apt checks the checksum.

If you must have something that’s not In your distro, do yourself a favour and install Docker and run your package inside there, much less chance of killing your system.

Source: I’ve been using Debian for over 25 years.

I’m talking about the reality of an organisation digging itself out of the hole created by projects such as described by OP.

I get the call from such organisations to help fix their issues and sometimes I can even help, more often than not it’s a time consuming effort (ie. expensive) to get to a point where the systems are in place to avoid the next catastrophe.

The reason that Microsoft keeps getting mind share and revenue is because there’s so much of that expertise around.

There’s loads of OSS professionals, myself included, but we’re a drop in the ocean by comparison.

In many cases an OSS deployment is the equivalent of “my nephew helped set this up” and it’s not helping the overall picture in the wider community.

If you’re going to deploy OSS, then you must consider the support implications before you start, anything else is unprofessional. License fees are insignificant by comparison.

Here’s three:

• A server with nobody supporting it for 13 years. It had a MySQL database with 743 columns. There was no documentation, served three organisations and hadn’t been backed up for at least 7 years.
• A server running a CMS for a dozen organisations that was running on failing hardware. No idea who built or didn’t support it.
• A server built by an employee 15 years ago, then supported by a “web company” who didn’t update it for 12 years, then “supported” by a Windows shop which was happy to charge the customer but hadn’t actually updated the server.

You’ll notice that I’m being deliberately vague.

All these share the exact scenario that the OP outlines. The organisations involved didn’t know that they were in deep trouble until well after the project instigator departed. No documentation, no updates, no training, handover, nothing beyond a set of credentials.

Er is er altijd wel eentje …