virr

joined 1 year ago
[–] virr@lemmy.world 2 points 1 month ago

Open EVSE, but any charger that support OCPP in theory can be controlled by any software. I do not have an OCPP EVSE installed (or any EVSE yet), so no idea if it actually works.

[–] virr@lemmy.world 9 points 8 months ago (7 children)

CEC (technically I think displayport could support it, but generally isn't implemented) and ethernet up to 100Mbps.

[–] virr@lemmy.world 37 points 9 months ago (6 children)

This is why we prefer to buy physical media, getting a digital with it is nice, but physical is key.

It wasn't even me was pushing for us to get physical media, it was my spouse. Of course my plex server the house probably helped. But after a few "forever" is only until next month, or shows completely disappearing altogether from any streaming, they started pushing for more physical media.

[–] virr@lemmy.world 3 points 10 months ago

From the original ruling it sounded like having the even just the sensor in the watch would be infringing. It sounds like these are new watch they are importing, but the article doesn't make it clear if that is the case.

[–] virr@lemmy.world 5 points 11 months ago

Depends on specific machine setup and how good the backup is.

Backup requirements for /usr there are sticky bits set on some binaries. That needs to be preserved. In all cases soft links likely need to be preserved for things to work correctly on future package installs. Hard links can be problematic, but if you have a large enough drive or not that many it wont matter. Running package verification can be help after restore to make sure everything looks right. If running a Linux system with SELinux in enforcing mode (RHEL on many derivatives), then the security context will also need to be preserved BUT running a relabel will probably work if the security context was not included in backups. Sometimes running the relabel process wont work if there are files that needs a specific security context but are not listed in the security context database. Can't provide more details because most of my experience with that is on systems we just replace (LSPP custom labeling resulted in systems that if you booted into permissive would then be unbootable, so they were just reinstalled once any debugging was done).

For /boot things can get tricky depending on the distribution, what boot manager is used, and /boot was a separate partition or not. Basically the boot manager (probably grub) needs to know how to find the files in boot so it can load the kernel. In most cases if you restore /boot and rerun the tools to update the boot manger everything will be fine. BUT some distributions, hardware setups, or dual boot configurations are more complicated, so extra work might be needed.

You didn't mention /dev, which is all special files. These don't need to be restored, just make sure the right processes recreate them. There are tools to do this, hopefully the packages are installed. Or boot from a rescue disk and fix it. Look up instruction for your specific distro.

[–] virr@lemmy.world 8 points 11 months ago

More of it will display the LOG_EMERG message instead of just stopping without displaying anything.

There are some headless servers I'd prefer to just reboot, but unless actual hardware is faulty I would not be too worried about it.