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.
There are cases where you’d want a particular site or subfolder to be easily accessible from specific locations (like the intranet) but apply a minimum protection from public eye for the wide internet.
Apache does support this mixed configuration for its sites through its htaccess functionality.
When things have been running for long enough various updates and configuration changes start adding up with leftovers bound to cause an issue sooner or later.
With Virtualmin, one such issue is the system’s inability to automatically update its scripts to newer versions based on the incorrect detection that an older PHP version is running on the server instead of the actual one.
OpenWRT upgrades itself by saving configuration files from known locations (plus manually defined files), overwriting the partition with the latest firmware and then restoring the saved configuration.
This usually works for the configuration itself, however the process doesn’t take care of any custom packages that were previously installed manually (either through LuCI or with opkg). These packages need to be noted down beforehand and then reinstalled.
There are times when you need to filter out what some hosts in the network can or cannot do. When you have a router running OpenWRT this can be done at the firewall level.
But if you’re not much into advanced configuration and just want to completely block out some network hosts from reaching the internet (and hence phoning home) then it’s a lot simpler to do this directly from the DHCP and simply leave them without a DNS and gateway configuration.
If you’re looking for a quick and simple method to redirect your plain HTTP site visitors to the SSL edition without fancy server-side configuration (or asking your host for help), this can be easily done through the ubiquitous .htaccess file present and supported on most Apache-powered hosting services.
