- Install
restic
andautorestic
sudo mkdir -p /var/cache/restic
- Set up
/etc/autorestic.yml
roughly as follows:
backends:
mybackend:
# Your backend options here, see the documentation
global:
all:
cache-dir: /var/cache/restic
restic
and autorestic
sudo mkdir -p /var/cache/restic
/etc/autorestic.yml
roughly as follows:backends:
mybackend:
# Your backend options here, see the documentation
global:
all:
cache-dir: /var/cache/restic
FEXBash-mkurz@mkurz-macbook-pro:~> LD_DEBUG=files glxinfo32 | |
347: | |
347: file=libxxhash.so.0 [0]; needed by /usr/bin/FEXInterpreter [0] | |
347: file=libxxhash.so.0 [0]; generating link map | |
347: dynamic: 0x0000ffff96569d30 base: 0x0000ffff96550000 size: 0x000000000001a010 | |
347: entry: 0x0000ffff96550000 phdr: 0x0000ffff96550040 phnum: 7 | |
347: | |
347: | |
347: file=libstdc++.so.6 [0]; needed by /usr/bin/FEXInterpreter [0] | |
347: file=libstdc++.so.6 [0]; generating link map |
Preface: I f**king love where Asahi linux is going. After installing it on my macbook pro a year ago I have had an absolute blast getting it all up and running. I haven't ever had so much fun just enjoying the experience of an operating system.
I am one of those apple fanbois who setup a mac and a Studio Display. I have been itching to connect my display. But as I eagerly await USB-C DP (alt) mode support in Asahi I must make do with using the HDMI port of my Asahi Linux MacBook Pro. For those playing along at home, the Studio Display has only a usb-c port for display input. People (including Apple's own ambiguous advertising) mistake this to be a Thunderbolt only display however it is very happy connecting to any device that supports USB-C DP (alt) (I was even using my phone as a daily driver with the display for a cheeky bit there). Perhaps that's my fuzziness around the topic of USB-C/Thunderbolt3/4
I have been successful in connecting my display to th
Setup org.freedesktop.secrets
the easy way with KeepassXC in Github Desktop
You might want to quickly authenticate with your Github Account to avoid having to manually configure GIT.
Although if you're using a lightweight distribution you might discover that you have to manually find a provider for org.freedesktop.secrets
.
I encountered this problem and wanted to share my thoughts and general pointers from what I've learned!
<!doctype html> | |
<html lang="en"> | |
<head> | |
<meta charset="utf-8" /> | |
<title>Diff to HTML by rtfpessoa</title> | |
<!-- | |
Diff to HTML (template.html) | |
Author: rtfpessoa | |
--> |
The included script 'widevine-flash_armhf.sh' fetches a ChromeOS image for ARM and extracts the Widevine binary, saving it in a compressed archive. Since it downloads a fairly large file (2Gb+ on disk after download) it is recommended that you run the script on a machine that has plenty of disk space.
To install the resultant archive, issue the following on your ARM machine–after copying over the archive if needed:
sudo tar Cfx / widevine-flash-20200124_armhf.tgz
(Where 'widevine-flash-20200124_armhf.tgz' is updated to reflect the actual name of the created archive)
package foo; | |
import java.lang.reflect.Method; | |
import java.util.concurrent.CompletionStage; | |
import javax.inject.Inject; | |
import play.Logger; | |
import play.db.jpa.JPAApi; | |
import play.mvc.Action; |
I hereby claim:
To claim this, I am signing this object:
Create new filters and create new labels.
from:([email protected]) AND {"Patch Links" "approved this pull request." "requested changes on this pull request." "commented on this pull request." "pushed 1 commit." "pushed 2 commits." "pushed 3 commits."}
label: gh-pull-request