Posts

Create a basic Debian 13 VM using the QEMU CLI I wanted to build my step-by-step understanding of the QEMU CLI. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 sudo qemu-system-aarch64 \ -machine virt \ -cpu host \ -accel hvf \ -m 4G \ -drive if=pflash,format=raw,readonly=on,file=$HOME/vms/edk2-aarch64-code.fd \ -drive if=pflash,format=raw,file=$HOME/vms/debian-13/efivars.fd \ -drive if=none,id=hd,file=$HOME/vms/debian-13/disk.qcow2,format=qcow2 \ -drive if=none,id=cd,file=$HOME/vms/debian-13/debian-13.5.0-arm64-netinst.iso,media=cdrom,format=raw \ -device virtio-blk-pci,drive=hd \ -device virtio-blk-pci,drive=cd \ -netdev vmnet-shared,id=net0,start-address=192.168.222.2,end-address=192.168.222.254,subnet-mask=255.255.255.0 \ -device virtio-net-pci,netdev=net0 \ -device virtio-gpu-pci \ -device qemu-xhci \ -device usb-kbd \ -device usb-tablet \ -display cocoa This is the command that gave me a working Debian 13 ARM VM on my M5 MacBook Pro. ...

I had never actually used Nix, but have always wanted to play around with it. Looking into it I was immediately overwhelmed. In the end I followed a few guides, wrote some files and ran some commands and it worked. This however did not satisfy me and I wanted to know what actually happens, when I run nix or nix-darwin commands. In this post I wanted to share my journey a bit and explain nix from the bottom up as I understand it now. ...

Personal Kicad library conventions for symbol libraries. Inspired by the official KiCad Library Convention (KLC) but adapted for a fully specified component library. 1. Scope These conventions apply to all symbol libraries prefixed with MyLib_. Every symbol in these libraries should be fully specified. It represents one exact purchasable component with a pre-assigned footprint, datasheet, and distributor information. 2. Library Naming Libraries are named by function using the format: ...

Hello World This is my personal blog where I’ll talk about things I find interesting.