Badabinski

If you want extreme flexibility, use Arch Linux, since it makes it trivial to swap out which window manager you’re using. It sounds like you’re familiar with Linux at this point, so you probably have the requisite knowledge to give Arch a spin.

Niri is supposed to be a pretty interesting WM if you’re looking for something new. I’d be interested to hear why i3 was too much, since I found it to be pretty smooth to pick up.

Sheesh, it’s 5 GB with pnpm. Isn’t that meant to deduplicate dependencies?

Anywho, it looks like --prod isn’t being set in the Dockerfile, so dev dependencies are being included. I’m no node dev, but I remember this being something that people needed to set to shrink node_modules with npm. That might be an easy win.

journalctl -b -1 will show you the logs from the previous boot. journalctl -k -b -1 will do the same for the kernel logs. If you’ve rebooted again since, just use -2 instead of -1.

I don’t believe that does the same thing either. What if I lock my computer, sleep it, and step away for the day? I haven’t logged out, but my interactive session has ended.

Uptime shows how long the system has been up, not how long one has been interacting with the system.

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.

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.

Relevant XKCD.

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

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

Honestly, I don’t think the tooling would be too terrible. Ron Covell has been making crazy shit out of sheet metal using nothing but hammers and simple wooden forms for many years, and I think it might be possible for OP to do the same. Granted, it would be hideously time consuming and would require great skill, but I think it’d be doable.

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.

Anubis has worked if that’s happening. The point is to make it computationally expensive to access a webpage, because that’s a natural rate limiter. It kinda sounds like it needs to be made more computationally expensive, however.