Add a -f to your umount and you can clear up those blocked processes. Sometimes you need to do it multiple times (seems like it maybe only unblocks one stuck process at a time).
When you mount your NFS share you can add the “soft” option which will let those stuck calls timeout on their own.
I’ve got several full color Hue bulbs that are the most used lights in my house. I haven’t had a single failure in a decade.
I was more than a little annoyed when they decided to stop supporting my original controller for them though.
This was a separate outage unrelated to CrowdStrike a few hours earlier that took down a couple of airlines as well.
A majority of the VMs in the Azure CentralUS datacenter went down due to some sort of backend storage issue.
Edit: I guess I should have read the article they do say CrowdStrike. They seem to be implying that they were one event when the cloud services outage was earlier and unrelated. I had heard about grounded flights during the first outage as well. So they likely are combining the two events here.
I would think most wifi jamming is just deauth attacks. It is much easier to just channel hop, enumerate clients, and send them deauthentication packets.
This way you don’t need a particularly powerful radio/antenna, any laptop/hacking tool with Wi-Fi is all you need. There are scripts out there that automate the whole thing, so almost no deep knowledge of wifi protocols are required.
WPA3 has protected management frames to protect against this but most IoT cameras probably don’t support WPA3 yet.
Updates for CrowdStike are pushed out automatically outside of any OS patching.
You can setup n-1/n-2 version policies to keep your production agent versions behind pre-prod, but other posts have mentioned that it got pushed out to all versions at once. Like a signature update vs an agent update that follows the policies.
One nice thing about KDE compared to most of the other DEs is that the window manager (kwin) is separate from the underlying components, and it can be replaced!
There are many walkthroughs like this one out there: https://github.com/heckelson/i3-and-kde-plasma
You get i3 for tiling window management but you still get to use KDE’s system settings to do configuration like display settings, themes keyboard shortcuts, etc, just like you did before. You can also pick and choose which parts of the KDE desktop you want to keep (menu, krunner, etc)
Since i3 is just a window manager and is lacking all of that system level stuff it really rounds out i3 to feel like a full DE instead of having to piece together other tools to do those things.
If you are accessing your files through dolphin on your Linux device this change has no effect on you. In that case Synology is just sharing files and it doesn’t know or care what kind of files they are.
This change is mostly for people who were using the Synology videos app to stream videos. I assume Plex is much more common on Synology and I don’t believe anything changed with Plex’s h265 support.
If you were using the built in Synology videos app and have objections to Plex give Jellyfin a try. It should handle h265 and doesn’t require a purchase like Plex does to unlock features like mobile apps.
Linux isn’t dropping any codecs and should be able to handle almost any media you throw at it. Codec support depends on what app you are using, and most Linux apps use ffmpeg to do that decoding. As far as I know Debian hasn’t dropped support for h265, but even if they did you could always compile your own ffmpeg libraries with it re-enabled.
The mediainfo command is one of the easiest ways to do this on the command line. It can tell you what video/audio codecs are used in a file.
To answer this you need to know the least common denominator of supported codecs on everything you want to play back on. If you are only worried about playing this back on your Linux machine with your 1080s then you fully support h265 already and you should not convert anything. Any conversion between codecs is lossy so it is best to leave them as they are or else you will lose quality.
If you have other hardware that can’t support h265, h264 is probably the next best. Almost any hardware in the last 15 years should easily handle h264.
Yes they are generated locally, and Dolphin stores them in ~/.cache/thumbnails on your local system.