if it’s an app, it’s not n OS, and does not replace an OS.

People want to replace the OS to get rid of forced data mining, forced updates, other limitations, and to be able to install other kinds of apps

scraping bots are expected to visit it, nowadays more than in previous years. a few of them are search engines, but there’s a lot of scraping for AI training, both on text and image data.

because it’s much less important and so much less risky

isn’t this prone to a

 || rm -rf /

or something similar at the end of the URL?

if you can docker exec, you have a lot of privileges already, so be sure to make sure this is not a danger

the French forgot about when to use guillotines decades ago

one more thing I remembered when re-reading the title: I think you can send messages to the VM using the qm command. it stands for qemu monitor, basically its a management tool

my solution to this is to only deal with the UPS in proxmox. it shuts down everything if the battery goes below a certain level.

I think you can configure nut to run a few scripts when something changes around the UPS. you could have a script that sends an alert through ntfy, and/or the web services that you want to use for this, but I’m not familiar with the notification system of nextcloud and truenas

it only works for hiding ads, it is powerless to protect any of your privacy anymore. ublock origin is much more than an adblocker, but ubo lite is basically just google’s mockery

would running nut-monitor in the VMs fit your use case?

oh, that’s good to know! iirc that’s the same reason it happens on windows too

oh, that’s good to know! iirc that’s the same reason it happens on windows too

oh yeah now that you say, SMB/CIFS mounted share if connection is no more. when I experienced this, it was temporary though, because there’s a timeout which is half (or double?) of the configurable reconnection timeout. but now that I think of it, I’m not sure if it made it unkillable.

killall just kills all instances of a program, not everything.

and also, long pressing the power button should just shut it down, no?

on windows a process can get in a state so that it is impossible to make it go away, even with process explorer or process hacker. mostly this also involves the bugged software becoming unusable.

I encounter such a situation from time to time. one way it could happen is if the USB controller has got in an invalid state, which one of my pendrives can semi-reliably reproduce. when that happens, any process attempting to deal with that device or its FS, even the built-in program to remove the drive letter, will stop working and hang as an unkillable process.

only if that feature wouldn’t have a massive memory leak… can’t update even to 10.9 because it crashes the whole system the first time it tries to rescan a library.

there’s an issue, and they have a hard time figuring out the problem.

you should be able to turn it up always, to some extent. it’s in the settings on web

I have recently discovered what was causing this to me for years. It was IP specific port bindings. Ports of a few containers were only bound for the LAN IP of the system, but if DHCP couldn’t obtain an IP until the Docker service started its startup, then those containers couldn’t be started at all, and Docker in it’s wisdom won’t bother with retrying.

The reasons to move my compose stacks to separate systemd services are counting.

I suspect that the JSON file is for the Nix package manager

the only game I have that has cards are the portal series, the others I haven’t experienced because I don’t play with games that have them. Are hats and loot boxes Valve’s fault, though?

well fortunately valve is enshittificating at a pretty slow pace, then