Technology

Debian 11 arm64 cd image boots and installs just fine under UTM (QEMU) on an Apple M1 Mac, but when the VM reboots you’ll be thrown to the UEFI screen instead of seeing the usual GRUB boot menu with no clue as to what the problem might be. Here’s a workaround that will let you boot from the install disk again. Go to Boot Maintenance Manager Boot Options Add Boot Option Select the volume, it should be the only volume there Select EFI Select debian Select grubaa64.efi Give the Boot Option a description Commit your changes Now go back and […]

If you’ve come here looking for a solution to your Mac locking up everytime you enable iCloud Photo Library, you’ve come to the right place. You’re probably enabling it for the first time and your system keeps freezing for some unknown reason, either not being able to wake from sleep or going completely unresponsive. The same thing happened to us. After pounding our heads against the wall for a good week, we noticed the library had all manner of weird files in there like AVI and PSD. Photos did not like this one bit as it to tried to convert

Upgrading from Debian 8 (Jessie) to Debian 9 (Stretch) will retain the old interface names (eth0, eth1). This was intentionally done to provide a path of least disruption when it came to upgrades. New installations will automatically use the new naming convention.If you’d rather migrate to the new interface names, remove the following file: /etc/systemd/network/99-default.link Then edit /etc/network/interfaces accordingly with the new interface name.

If you’ve recently upgraded to Elasticsearch 2.0 and Logstash 2.0, you may find that Logstash is no longer able to create indexes in Elasticsearch, as evidenced by the following error in the Elasticsearch logs. [code lang=text] MapperParsingException[Mapping definition for [geoip] has unsupported parameters:  [path : full]] [/code] This error was due to a bug in the elasticsearch output plugin of Logstash 2.0 which has since been fixed, but your logstash template within Elasticsearch might still contain the old mapping. To remedy the situation, run the following command to prune the old template: [code lang=text] curl -XDELETE http://localhost:9200/_template/logstash?pretty [/code] That should do it.