on linux 4.19, I get
error creating new backup file '/var/lib/dpkg/status-old': Invalid cross-device link
when trying to install stuff on a ubuntu docker container. this seems to be an issue with metacopy https://www.spinics.net/lists/linux-unionfs/msg06109.html
issue can be worked around by running
| # $Id$ | |
| # Maintainer: Tom Gundersen <[email protected]> | |
| # Contributor: Travis Willard <[email protected]> | |
| pkgname=nss-mdns | |
| pkgver=0.14.1 | |
| pkgrel=1 | |
| pkgdesc="glibc plugin providing host name resolution via mDNS" | |
| arch=('x86_64') | |
| url="http://0pointer.de/lennart/projects/nss-mdns/" |
| [Unit] | |
| Description=AMD Radeon Config | |
| Before=claymore.service | |
| [Service] | |
| Type=oneshot | |
| ExecStart=/bin/sh -c 'for i in 3 4 5 6; do /home/miner/amd/ohgodatool/ohgodatool -i $i --set-fanspeed 50 --mem-state 2 --mem-clock 1980 --core-state 7 --core-clock 1200; done' | |
| [Install] | |
| WantedBy=multi-user.target |
Past August 2024, Authy stopped supported the desktop version of their apps:
See Authy is shutting down its desktop app | The 2FA app Authy will only be available on Android and iOS starting in August for details.
And indeed, after a while, Authy changed something in their backend which now prevents the old desktop app from logging in. If you are already logged in, then you are in luck, and you can follow the instructions below to export your tokens.
If you are not logged in anymore, but can find a backup of the necessary files, then restore those files, and re-install Authy 2.2.3 following the instructions below, and it should work as expected.
| silly gist hack, why do we need you? :( |
| diff --git a/devices/MKL27Z4/gcc/startup_MKL27Z4.S b/devices/MKL27Z4/gcc/startup_MKL27Z4.S | |
| index 961af8d..b249b4b 100644 | |
| --- a/devices/MKL27Z4/gcc/startup_MKL27Z4.S | |
| +++ b/devices/MKL27Z4/gcc/startup_MKL27Z4.S | |
| @@ -47,7 +47,7 @@ __isr_vector: | |
| .long __StackTop /* Top of Stack */ | |
| .long Reset_Handler /* Reset Handler */ | |
| .long NMI_Handler /* NMI Handler*/ | |
| - .long HardFault_Handler /* Hard Fault Handler*/ | |
| + .long HardFault_HandlerAsm /* Hard Fault Handler*/ |
The official installation guide (https://wiki.archlinux.org/index.php/Installation_Guide) contains a more verbose description.
| Price breakdown vs DigitalOcean, Vultr and Linode: | |
| RAM / CPU Cores / STORAGE / Transfer | |
| $5/mo | |
| LightSail: 512MB, 1, 20GB SSD, 1TB | |
| DO: 512MB, 1, 20GB SSD, 1TB | |
| VULTR: 768MB, 1, 15GB SSD, 1TB | |
| $10/mo |
| This is a patch to the Linux QMI drivers provided by Sierra Wireless | |
| (http://source.sierrawireless.com/resources/airprime/software/usb-drivers-linux-qmi-software-s2,-d-,25n2,-d-,38/). | |
| These drivers incorrectly assign `usb_serial_generic_resume` to a `struct usb_driver.resume` when it can only be assigned | |
| to a `struct usb_serial_driver` (and the driver already provides one). Instead, the `struct usb_driver.resume` should get | |
| `usb_serial_resume` from the generic usb-serial driver which does the delegation to the function passed into the | |
| `struct usb_serial_driver.resume`. The `struct usb_driver.reset_resume` is removed as that's added automatically by the | |
| kernel's USB init code. | |
| Use this patch if you get the following errors compiling: |
Using ISC DHCPD's concept of classes, we have a simple and powerful way of provisioning Polycom VoIP phones.
In the main body of the dhcpd.conf file (outside of any subnet declarations), we are going to define a couple custom Polycom options, then define the class, and match statements - which determine when the class is applied to DHCP clients. The class definition is also a good place to include some global options that will be applied to all Polycom clients, regardless of what subnet they end up on.
For the purposes of these examples, we're going to pretend our TFTP server is 10.0.1.2, and we are going to provision our phones to boot up on VLAN42 (10.0.42.0/24).
# Custom options used by Polycom clients
option polycom-vlan code 128 = text;