I think /mnt is where you manually mount a hard drive or other device if you’re just doing it temporarily, and /media has sub folders for stuff like cdrom drives or thumb drives?

That or Ansible, if you will have a machine to deploy from

Zoneminder was cool when it was the only game in town, but didn’t it save “videos” as a folder of JPEGs of frame grabs?

Yeah, always check all of this stuff. Server hardware gets a lot more updates than like gamer board BIOS, companies invest high millions, even low billions in this stuff and they expect problems to be address promptly for that kind of cash.

Check for any peripherals or cards, too. RAID, backplanes, networking cards; drivers, firmware, anything.

What’s closed about OPNSense?

No, no - legit! Do go on.

I can’t event get my town to put the trash holiday schedule in an iCal file.

Hades

Exactly. These kind of things happen from time to time; hell even big corpo OSes mess up. They said they’d taken time to fix their process to prevent this problem happening again.

If it becomes a pattern I’d become concerned. So far, it was inconvenient.

I understand

No, no clearly don’t.

I don’t think it’s “kinda dumb” to point out the issue all, unless you’re an insufferable twatwaffle like 90% of the fucking STEM community in 2024, who can never be wrong or challenged.

Like, I’d consider myself pretty progressive, maybe even “woke” if that still has any meaning left, and even I might have just used male pronouns because I myself am male;’not for malicious reasons but just because I wasn’t thinking in that moment.

But if I was like “oh yeah, that makes sense, and cool you even did the work of fixing it for me! Merged.” and went about my day, no one would have brigaded me, no one would have posted it all over socials, there wouldn’t be blogs and articles, and I’d probably have a leg to stand on if anyone still wanted to make a big deal.

The way this dude reacted was a self-report. The community was right to push back, even if some people ended up taking it too far.

I’m not familiar with using USB drives, but on any bare-metal system don’t use /dev/sdX but instead use /dev/disk/by-id/<big long disk identifier> in your fstab/cryptab etc. Even if you switch ports/bays, or your devices come up in a weird order after a reboot, config always points to the same physical disk. Way less stuff breaks.

God they’re so expensive now. I bought a 24-port backplane for $37 like 3 years ago and the same one is now $120

Yeah, ok? The fresh mechanics Pokemon has needed for a long time now. Also, still rounding up ‘mons to build a team to accomplish goal.

It was similar enough that Nintendo had to tell its fans to shut the hell up about it.

Palworld is the facelift Pokemon needed.

Man, he admitted he was guilty.

I don’t recall Nintendo trolling.

I do recall Nintendo, in the most polite and businesslike way possible, telling its incessant dickriders to stop flooding its communication channels with the breaking news that someone made a game with a Pokemon-adjacent concept.

Yeah that’s kind of the point.

(Also wtf are you smoking? “Travel the world collecting animals to be on your team” is the core concept)

Seems if the messages are sent in an inherently insecure fashion, all one would need to do is set up an instance that purposefully does not filter out all the things it’s supposed to be kind/competent enough to filter out, and boom it has everything.

NFS is always cranky for me, and you can’t get it to use symlinks at all (yeah Samba’s implementation is janky but at least it exists)

It’s UID/GID 10000 on the host because you are using an unprivileged LXC container. Unprivileged means that “root” inside the container (which is just a user space of the host with access restrictions) is user 10000 on the host - this is so that files and processes inside the container don’t run with the real UID zero, where they could plant a malicious file, or run a malicious program that escapes containment that ends up with root access on the host.

Quickest way to make this work over samba is to force user 10000 and force group 10000. That way everything connecting to Samba would see the files as their own.

Honestly the better solution is to make your software inside the containers run with a local non-root user (which would be something like 10001) and then force samba to use that. Then nothing is running as root in or out of the containers. Samba will still limit access to shares based on the samba login, but for file access purposes it will still use the read/write levels of your non-root user (because of the force- directives)