I have been using Jellyfin as my main media player more and more lately. I’ve always been a fan of VLC and its compact-ness, but I found a some pluses in Jellyfin over VLC. However, there are things that bother me with Jellyfin as well. One of them is the playback controls which simply take way too long to disappear when not used.
If you’ve tried changing the MAC address on a recent Ubuntu VM running under KVM/QEMU, you may have noticed that changing the address in the VM configuration on the host yields no result in the guest machine. Also, a change done using either Virtualmin’s configuration or the command line on the guest doesn’t survive a reboot.
LuCI (the OpenWRT web UI) has a default session duration of 1 hour, after which an idling session will be logged out and require a new login.
That can quickly become annoying if you’re one to just leave tabs open and stare at statistics.
From WireGuard’s perspective, there is no server and client – all points in a WireGuard network are called peers, and they can connect to each other without a central point and not necessarily in a star topology. However, in this particular configuration scenario and because one peer is central to the whole infrastructure I’m setting up (as it’s the only one to always have a static public IP address, open ports and it can also be used to tunnel all other peers’ traffic), I’m calling it a server – while all other peers I will consider clients.
Some of the smart power plugs I’m using to monitor power usage appear to report incorrect information when viewed in Home Assistant through the Tuya bridge. The information is fine directly in the Tuya app, so the app is probably doing some data processing behind the hood.
Unfortunately, there’s no way of correcting this directly in the entities as managed by Home Assistant. To display (and use) the right sensors values in HA we need to (manually) create some aliases and mathematically correct the values.
By default, Jellyfin on CentOS logs to the main system log. This isn’t an issue except in odd instances, like for example when part of library is located on a remote network attached storage that isn’t permanently available.
This makes Jellyfin log thousands of lines of warnings when (re)scanning the libraries and hits the missing media locations which in turn causes lfd to send out alerts about the syslog getting flooded.
Accessing host storage directly from a KVM guest is useful in many cases, for example when the storage is or grows large over time and it would be inefficient to hoard large volume of data inside the virtual machine itself.
Sometimes crazy changes need to be performed to adjust how storage is laid out and arranged. In this instance converting an existing (but non-critical) RAID1 mdadm array to RAID0 (even less critical) is the far-fetched requirement.
Firefox 91 changed the downloads behaviour by setting the download action for all file types to save regardless of the previously set option. Additionally, it also changed the functionality to use the default Downloads folder even for temporary downloads.
For experimental reasons I was running a RAID0 array (the speed!) off of two Sandisk Cruiser Mini USB sticks connected to a Raspberry PI.
As expected, due to wear and tear one of the flash memories eventually failed causing the array to go read-only and crash everything that was writing to it, including the array activation.
Intel Boot Utility, Preboot Images, EFI Drivers package, Ethernet Flash Firmware Utility, Intel Boot Agent or how to make a mess of things with too many names and tools.
Same as one can never have enough memory, one can also never have enough disk space. Luckily, on virtual machines that’s easier to resolve than with physical hardware. But increasing the disk space available for a VirtualBox machine is still a multi-step process.