Badabinski

It does! The ease of exporting/importing mod packs as codes is part of what really sold me on it. r2modman’s UX around that task leaves something to be desired imo

If you’re using r2modman, you should check out Gale. It’s basically a drop-in replacement that’s WAY faster and has far better UX in my opinion.

People are submitting AI generated bug bounty reports to projects and are hiding the fact that they’re AI.

EDIT: I probably should have linked this one.

If you want more help with Bash in the future, this is the best resource I’ve found in 13 years of writing bash professionally: https://mywiki.wooledge.org/EnglishFrontPage

Bash FAQs and pitfalls are the primary sections to look at there.

Thank you for providing the easiest and most portable answer. This will handle files with special characters perfectly unlike most of the responses here which rely on a while loop (to say nothing of a for loop ).

Shell scripts are one of the worst possible applications of an LLM. They’re trained on shit fucking GitHub scripts, and they give you shit in return.

You may have a bit of a hard time finding something that’s completely FLOSS that’s not on the older side (the sar visualizer being a Java desktop application being a consequence of that age). There are various ways to dump resource usage into a time series database like Prometheus (Apache2), InfluxDB (Apache2/MIT), or VictoriaMetrics (Apache2) and then visualize it with a frontend (Grafana, APGL). The database is going to be the tricky part. All of the time series DBs I’m aware of are permissively licensed. Grafana may be a good fit for you, however. It’s written in Go so it’s relatively light, although it obviously requires a browser to interact with.

It does, the repo is tagged as AGPL.

OP is in the US, so no 3 phase power unfortunately ):

Was this done according to proper clean-room design principles? If so, then imo the GPL is still working as intended. The company had to spend a fuckton of money and time getting one engineer to read the source and describe what was done to other engineers, and then ensure that one engineer never ever worked on the project again.

If they didn’t do that then they violated the GPL and someone should report them to the SFLC.

Relevant XKCD.

This is the most important piece of information. You should edit the post and/or title to make this more clear.

I hadn’t even thought of that! I did some oxyacetylene welding many moons ago and I remember the heat being absolutely intolerable at times.

I do machining as a hobby now and I’d really like to filter out cutting oil smoke. My biggest fear using a PAPR is my shop is the hose—I’d need to find a way to keep it REALLY close to my body. I don’t want to get pulled into my lathe face-first.

I very much want a PAPR as well. I seem to recall that there were some units that came out of COVID that are somewhat cheaper, at least.

Open source can be enshittified. FOSS with many contributors should be basically proof against being fucked with.

the f stands for file. The c manpage has some details on how it works: https://www.man7.org/linux/man-pages/man2/flock.2.html

CAD was a big problem for me as well. I’ve been happy enough with OnShape (coming from Autodesk Inventor), but the extreme SaaS nature of it makes me worry.

It also lacks any form of dependency management AFAICT. I don’t think there’s any way to say you depend on another service. I’m guessing you can probably order things lexically? But that’s, uh, shitty and bad.

I wrote and maintained a lot of sysvinit scripts and I fucking hated them. I wrote Upstart scripts and I fucking hated them. I wrote OpenRC scripts and I fucking hated them. Any init system that relies on one of the worst languages in common use nowadays can fuck right off. Systemd units are well documented, consistent, and reliable.

From my 30 seconds of looking, I actually like nitro a bit more than OpenRC or Upstart. It does seem like it’d struggle with daemons the way sysvinit scripts used to. Like, you have to write a process supervisor to track when your daemonized process dies so that it can then die and tell nitro (which is, ofc, a process supervisor), and it looks like the logging might be trickier in that case too. I fucking hate services that background themselves, but they do exist and systemd does a great job at handling those. It also doesn’t do any form of dependency management AFAICT, which is a more serious flaw.

Nitro seems like a good option for some use cases (although I cannot conceive why you’d want to run a service manager in a container when docker and k8s have robust service management built into them), but it’s never touching the disk on any of the tens of thousands of boxes I help administrate. systemd is just too good.

Just journalctl | grep and you’re good to go. The binary log files contain a lot of metadata per message that makes it easy to do more advanced filtering without breaking existing log file parsers.