which I found via rotatedlife's post in
https://www.reddit.com/r/MacOS/comments/74scld/unable_to_turn_on_filevault_on_high_sierra_apfs/
| #!/bin/bash | |
| # start up my Arch machine | |
| # root disk: | |
| # dd if=/dev/zero of=root.img bs=1000000 count=4000 conv=sparse | |
| # scratch disk is for moving data in and out without networking | |
| # e.g. tar -xzvf /dev/vdb | |
| # dd if=/dev/zero of=scratchdisk.img bs=1000000 count=2500 conv=sparse | |
| data=$HOME/archbox |
| #!/bin/bash | |
| # otel-cli-ideas.sh - some ideas I'm playing with for otel-cli to cover some | |
| # use cases where manual spans or exec don't quite do the trick | |
| # | |
| # another cool outcome is you could run this without the collector in some | |
| # cases without spamming your OTLP endpoint... | |
| # | |
| # I hope to OSS otel-cli under Apache 2 in early April 2021. | |
| # maybe it could background itself and wait for events on a unix socket? |
| receivers: | |
| otlp: | |
| protocols: | |
| grpc: | |
| endpoint: "127.0.0.1:55680" | |
| # opentelemetry-ruby only supports http for now | |
| http: | |
| endpoint: "127.0.0.1:55681" | |
| processors: |
| #!/usr/bin/env ruby | |
| # run the otel collector with otlp/http enabled and turn on debug logging | |
| # so you can see it print spans as they go through... | |
| # | |
| # configuration: | |
| # export OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:55681 | |
| # | |
| # first iteration I thought I had an easy repro because I had set | |
| # OTEL_RUBY_BSP_START_THREAD_ON_BOOT=false | |
| # so don't do that :) It's almost never what you want. |
| #!/bin/bash | |
| # start up my Arch machine | |
| # for this to work I had to extract kernel & initramfs from the ISO | |
| # which is a surprisingly a pain in the butt on OSX but easy enough | |
| # to find on Google, tldr add 2K of zeroes to the front of the ISO | |
| # then it'll mount just fine | |
| # to make root disk: | |
| # dd if=/dev/zero of=root.img conv=sparse bs=1000000 count=20000 |
| func main() { | |
| input := []string{ | |
| "a", | |
| "b", | |
| "c", | |
| "foo", | |
| } | |
| data := make(map[string][]string) |
| #!/usr/bin/perl | |
| # this needs a serious cleanup/rewrite - it was hacked together | |
| # very quickly for a completely different purpose many years ago | |
| # and has grown in the worst organic way since | |
| # but ... it does work fairly well so it persists | |
| # Copyright 2007-2011 A Tobey <[email protected]> | |
| use strict; | |
| use warnings; |
| #!/bin/env python3 | |
| # | |
| # this is NOT a human-facing tool | |
| # | |
| # This is to replace the legacy data files being used to populate | |
| # variables in a shell script and instead get them from the vars | |
| # files even though that still feels weird. | |
| # | |
| # Example: | |
| # azs=$(yamlpath.py roles/cassandra/vars/clusters.yml clusters/multitenant-us-east-1/availability_zones) |
This is a quick & dirty way to attach an Akai MPK mini 2 USB MIDI controller to Linux so the Linux machine can act as its synthesizer. This approach should work for any modern USB MIDI instrument.
I looked around on the web and, surprisingly, I didn't find any simple options for quickly starting Fluidsynth up and wiring it to a MIDI controller for simple keyboard usage. There are a few out there that involve using Qsynth which is cool but I didn't want a GUI for something relatively simple.