If authorized by the school IT department and policy, yes. Ask them, not us.

I would just download them. Already ripped, encoded, and compressed.

For up to 16 endpoints or something like that, yes.

I don’t put it on the Internet.

I have automatic updates enabled and once in a while I scan with Nessus. Also I have backups. Stuff dying or me breaking it is a much greater risk than getting hacked.

What laptop? BIOS option?

I don’t think static linking is that difficult. But for sure it’s discouraged, because I can’t easily replace a statically-linked library, in case of vulnerabilities, for example.

You can always bundle the dynamic libs in your package and put the whole thing under /opt, if you don’t play well with others.

Android is licensed under the Apache license 2.0, which is an open source license. Their Linux kernel modifications are licensed under the GPL v2. https://source.android.com/license

Accepting contributions is not required to be open source.

What’s in the radarr log? You have your downloader configured, enabled, and tested I assume?

What are the crazy historical reasons? As far as I know, running six ttys and one graphical session, in that order, has been standard.

The really crazy historical way to test for crashes is num/scroll/caps lock. That’s handled by a very low-level kernel driver. If those are responsive, it’s probably just your display (gpu, X, wayland, or something) that’s locked up. If they’re unresponsive, your kernel is locked up. (If you’re lucky, it’s just gotten real busy and might catch up in a minute, but I’ve only seen that happen once.)

Anything that might interfere with sleep. Literally any attached device might have a buggy driver.

I don’t see a list of hardware in your edit.

Stop exposing services like these to the Internet. If you need remote access, use a VPN.

You don’t need to own a domain either. Use a free dynamic DNS provider.

And if you don’t need remote access, don’t bother with that at all. Just run a local DNS server with records for these services with anything under the .internal TLD. Or even just IP address.

HTTPS can come later. It’s really not important for traffic that’s not sensitive, like no passwords or whatever.

Correct. We will, of course, be able to create diffs between the released versions, for the whole project or for individual files (assuming they haven’t moved around).

Misleading headline. Instead of public repos, they’ll use source snapshots of each release. It’s technically correct because the development is going private, but the releases will remain open source.

Yes. And these posts should be sent there. I don’t come to the Linux community for shitposting.

You could just move the dir and leave a symlink in its place. It doesn’t solve the actual problem, but it’s much easier and will keep everything working just fine.

And because you can’t punch me in the face over the Internet (yet).

Have you tried tracing the issue? What is uptimekuma using for DNS? What do the logs on that server show?

Does the docker user have permission to that folder?

No, just a USB network adapter.