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.
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.
Sounds like the restraining order should have listed out additional remedies, or maybe even made her the sole owner.
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.
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.
This is a response to the very bad kids online safety act. See EFF's post for details on why it is bad: https://www.eff.org/deeplinks/2022/03/kids-online-safety-act-heavy-handed-plan-force-platforms-spy-young-people
EFF's article is better, but here are some of the details of why it is bad. The effect of kids online safety act will be censorship and tracking of kids online when research suggests that is counterproductive for the age group being added. Would require more detailed tracking of everyone, not just kids. Services likely would need to block certain content from everyone to reduce liability to a reasonable level. They would potentially be liable if kids got access to content even when it wasn't for kids no matter how the kids got access (lying, using someone else's account, bypassing filters, etc.). Content to be blocked is vague and open to be interpretation by the most conservative people in the US, which is obviously problematic. The previous COPPA needs updating, but the version of kids online safety act has so far been financially flawed.
How about a link to text instead of a video?
Here's the actually releases from github.com https://github.com/systemd/systemd/releases
Depends on environment.
Real hardware separate for a server partitions for: /home, /var, swap, sometimes /usr, sometimes /var/log/audit Depends on deployment requirements, and if a system is expected to run after filling up audit.
Real hardware for a at home desktop: /var, swap, maybe /home, or just one partition for / and one for swap.
Cloud: all one partition, put swap in a file if it is needed. Cloud images are easy to grow if it is just one partition. Cloud-init will handle that automatically with the right packages installed, no configuration needed. Swap partitions are unlikely to be the right size as they vary according to memory and memory varies according to instance/guest sizes. Swap makes auto growing root partition harder (cloud-init custom config injection required). Best practice is to size workload and instances to not need swap whenever possible.
with an aspect ratio of 20:1 across the entire dash.
vim-gnupg. If gpg-agent is setup and you connect with ssh with X11 forwarding enableed, gpg will popup it's passphrase entry box (even on WSL Windows 11 or Chrome OS). Easy and convenient if you have a pgp key.
If you just want to try to recover, PhotoRec This does require it to at least be able to power and have a raw device to look at, though it doesn't have to be able to be mounted. More than just photos can be recovered.
Had pretty close to the same results with PhotoRec vs commercial tools on windows.
CEC (technically I think displayport could support it, but generally isn't implemented) and ethernet up to 100Mbps.