diff --git a/homepage.content b/homepage.content index 9865f83..f6e5387 100755 --- a/homepage.content +++ b/homepage.content @@ -1050,6 +1050,367 @@ pre { /* DRY who? */ } +/blah/2024-06-24.html + +I'm sick today. Was pretty sick yesterday. Now pretty sick today. I keep +coughing up weird-colored mucus, not neon green but bits of brown and red and +yellow. Hopefully I'm well by tomorrow because I have a 9-hour shift I don't +wanna miss. + +I'm potentially going back to Maine soon. I need to go to get my stuff from my +grandparents, money from Troy, and hugs from M--. It'll suck but it'll be nice +to see M-- especially. + +: Contributing to Bonsai + +This guide explains how to start committing to Bonsai git repositories. It +walks the reader through setting up its freshly-installed, Bonsai-dedicated +system for cloning Bonsai repositories and committing to them. For a system +already in use it may be necessary for the reader to read the man pages for the +binaries used and use its own discretion with regards to its local setup. + +The following binaries are necessary to follow this guide: + +- git(1) +- gpg(1) +- ssh-keygen(1) + +And on the following systems, can be installed as follows: + ++------------------+----------------------------------------+ +| System | Installation command line | ++------------------+----------------------------------------+ +| Alpine | # apk add git gnupg openssh | +| Arch | # pacman -S git gnupg openssh | +| Debian | # apt install git gnupg openssh-client | +| OpenBSD | # pkg_add git gnupg | ++------------------+----------------------------------------+ + +## Cloning the git repository + +### SSH setup + +The following generates an Ed25519 SSH keypair, which will be used to clone, +pull from, and push to the Bonsai git repositories. This is optional. The +alternative is to use HTTPS authentication which is usually self explanatory +(the default if certain git commands are tried without SSH set up). + +``` +$ ssh-keygen -t ed25519 +``` + +ssh-keygen(1) will tell you where it put the public key; usually, this is +`$HOME/.ssh/id_ed25519.pub`. Open the Tebibyte Media Gitea instance, navigate +to the "SSH / GPG Keys" page in the User Settings, "Add Key" on "Manage SSH +Keys", and paste the contents of that file (it should end with `.pub`!) into +the prompt. + +### GPG setup + +Bonsai git commits must be signed with a GPG keypair. This generates a GPG +keypair for use with Bonsai. + +``` +gpg --full-generate-key +``` + +Generating an **`ECC (sign and encrypt)`** key with the **`Curve 25519`** and +an expiration date of **`1y`** tends to work well. + +This example is based on the example from +<https://docs.codeberg.org/security/gpg-key/&rt;, updated with the previous +settings. + +``` +public and secret key created and signed. + +sec ed25519/3AA5C34371567BD2 2021-06-06 [SC] [expires: 2025-06-25] + 6CD8F2B4F3E2E8F08274B563480F8962730149C7 +uid [ultimate] knut +ssb cv25519/42B317FD4BA89E7A 2024-06-25 [E] [expires: 2025-06-25] +``` + +The key ID here is `3AA5C34371567BD2`, the hexadecimal string after the key +type on the line prefixed with "sec". If the video terminal's display has been +cleared or the teletype runoff has been lost, the following command line will +print a list of keys present on the system: + +``` +gpg --list-secret-keys --keyid-format LONG +``` + +Given that the ID for the key to be used with Bonsai is `3AA5C34371567BD2`, the +following command line will export the public key for the keypair: + +``` +gpg --armor --export 3AA5C34371567BD2 +``` + +If the command errors out refer to +<https://wiki.archlinux.org/title +/GnuPG#Configure_pinentry_to_use_the_correct_TTY&rt; + +Then paste the public key into the appropriate prompt in the "SSH / GPG Keys" +page on the Gitea user settings. + +Now configure git to sign with the GPG key: + +``` +git config --global user.signingkey 3AA5C34371567BD2 +git config --global commit.gpgsign true +``` + +## All set + +Now clone a Bonsai repository, such as harakit: + +``` +git clone gitea@git.tebibyte.media:bonsai/harakit.git +``` + +If it works, you're probably all set. Thank you in advance for your +contributions! + + +/blah/2024-06-23.html + +Watched Smiling Frriends last night, and by that I mean I rewatched some of the +later of the first season and saw for the first time some of the second which +was really brilliant. Smiling Friends really holds up on rewatches. + +I can't wait to get my development environment finalized so I can work on +Bonsai stuff again. + +Bus pull-off strings are brilliant. The strings you pull to say you wanna get +off at the next stop? Brilliant. + +I feel nauseated but I'm going to work anyway because they wouldn't be able to +find cover for me and because a sore throat and sick tummy is all that stands +between me and six hours' income. + +I had a dream last night that I went to college and I desperately wish I could. +Being a full time student? That's the dream. I couldn't figure out how to fill +out the FAFSA or scholarship applications at 17 because I was severely +depressed, mostly from living with my parents, and was terrified I would remain +dependent on my parents. It's bonkers how badly bad parenting can fuck you up. +I'm speedrunning my good person tf ark. + +Local punks have been putting FREE PALESTINE stickers up and I wish to meet +them. I'm woefully uninformed regarding the Israel/Palestine conflict and wish +to remain that way as the few people I've met with strong opinions on the topic +have been pro-Israel and so strongly convinced of their righteousness that they +labelled their opposition anti-semitic. In my opinion that shuts down free +debate and poisons the topic for those who care about the human rights abuses +being committed on the Gaza strip. But I don't know, I guess time will tell. +The people who are fervently pro-Palestine seem to be pretty cool generally. +When in high school I asked my history teacher what the deal was with the +conflict. He said something like "I don't know if I could give you a good +overview of the issue. Both sides have done terrible things to each other. It's +complicated... really complicated." + +I've read a lot of arguments against SUID on Unix systems and remain totally +unconvinced. + +I changed my header again because the last one was corny as hell. + +: a paper I had in my string bag + +WHAT THE AMOUNT OF +POSSUMS YOU'VE SEEN +TODAY SAYS ABOUT YOU +0 you might be sober +1+ you are on some + fucked shit man. + this is a [...] + [...]. there are no + possums here. + + +/blah/2024-06-22.html + +I'm tired. I think I'll blah about my love life. + +2016-2017 - middle school "girlfriend". we held hands a couple times +2020ish - met a girl named Erika with whom I went on dates. one time I + described us as dating (as in, we went on dates) and she freaked + out over the idea of us dating (as in, a committed relationship) + and that ended that. found out later that i dodged a bullet +2021ish - high school "girlfriend". each other's Dirty Little Secret a la the + All-American Rejects. +early 2023- talked with this creature on-line on whom I had a massive crush but + ended it because I worried it would care too much about my constant + risk taking +early 2023- first kiss (19 years old) +mid 2023 - talked with the creature again. lost virginity (19 years old) +late 2023 - talked with this girl, started dating her, eventually broke up +early 2024- broke up with the creature + +I was very self conscious about being a hell of a late bloomer but am no +longer. I'm just not very much of a people person and my interpersonal +relations are few and far between. Some people really just aren't cut out for +steady relationships. + +Finding out most people use "dating" to mean that they are in a committed, +probably monogamous relationship really messed with me. To me that was "going +steady", and "dating" was, like it says on the tin, going on dates. Now I use +"talking" to mean speaking romantically, but only in that meaning sometimes, +which is baffling to me but actually works in communication, and "going steady" +to mean in some sort of relationship. + +I go out on dates with people I meet on-line pretty rarely. I met someone on +Tagmap and met them at a Whataburger and we sat in mostly silence for half an +hour, unable to think of conversation to make. Before that I went out a couple +times with the person that approved my Medicaid form but he kept feeling me up +without asking permission and it got on my nerves a lot. Then after those there +was a Space Force skid who was in title a cybersecurity analyst but didn't have +an opinion on the xz Jia Tan kerfuffle and didn't know much about UNIX or +programming. Really awful luck. + +: more adventures running openbsd in qemu + +This is slow as shit. How do I use QEMU as a hypervisor rather than aarch64-on- +aarch64 emulation? + +$ qemu-system-aarch64 \ + -enable-kvm -M virt -cpu host -m 512M \ + -bios "$HOME"/Machines/QEMU_EFI.fd \ + -device rtl8139,netdev=lan \ + -device virtio-rng-device \ + -netdev user,id=lan \ + -nographic \ + -hda "$HOME"/Machines/obsd.qcow2 + +Boot times down to <1min from multiple minutes. + +Serial console looks like shit. How do I SSH into this virtual shitbox? + +<https://www.baeldung.com/linux/qemu-ssh-host-guest&rt; + +# apt install bridge-utils +# brctl addbr br0 +# brctl addif br0 eth0 +# ip link set up dev br0 +# echo allow br0 >/etc/qemu/bridge.conf +# chmod 644 /etc/qemu/bridge.conf +# ip addr add dev br0 10.0.0.101/24 + +No dice on this so I give up. + + +/blah/2024-06-21.html + +: running openbsd in qemu + +$ qemu-system-x86_64 \ + -M pc -cpu qemu64 -m 512M \ + -device rtl8139,netdev=lan \ + -netdev user,id=lan \ + -nographic \ + -drive file="$HOME"/Machines/obsd.qcow2,media=disk,if=virtio \ + -cdrom install75.iso +[blank lines abridged] +SeaBIOS (version 1.14.0-2) +iPXE (http://ipxe.org) 00:02.0 CA00 PCI2.10 PnP PMM+1FF8F200+1FECF200 CA00 +Booting from Hard Disk... +Boot failed: not a bootable disk +Booting from DVD/CD... +CD-ROM: E0 +Loading /7.5/AMD64/CDBOOT +probing: pc0 com0 mem[639K 510M a20=on] +disk: hd0+* cd0 +>> OpenBSD/amd64 CDBOOT 3.65 +boot> +cannot open cd0a:/etc/random.seed: No such file or directory +booting cd0a:/7.5/amd64/bsd.rd: 4076463+1688576+3891240+0+708608 [109+464016+317 +541]=0xaa40e8 +entry point at 0xffffffff8100100 + +And then it hangs. What's going on? + +<https://www.reddit.com/r/openbsd/comments/l4c1zo + /openbsd_hangs_after_entry_point_at/&rt; +says perhaps I'm using a 32b processor rather than 64b. The software I'm +writing needs to work on 32b so whatever, let's try the i386 install75.iso. + +$ qemu-system-x86_64 \ + -M pc -cpu qemu64 -m 512M \ + -device rtl8139,netdev=lan \ + -netdev user,id=lan \ + -nographic \ + -drive file="$HOME"/Machines/obsd.qcow2,media=disk,if=virtio \ + -cdrom install75\(1\).iso +SeaBIOS (version 1.14.0-2) +iPXE (http://ipxe.org) 00:03.0 CA00 PCI2.10 PnP PMM+1FF8F470+1FECF470 CA00 +Booting from Hard Disk... +Boot failed: not a bootable disk +Booting from Floppy... +Boot failed: could not read the boot disk +Booting from DVD/CD... +CD-ROM: E0 +Loading /7.5/I386/CDBOOT +probing: pc0 com0 apm pci mem[639K 510M a20=on] +disk: fd0 hd0+* cd0 +>> OpenBSD/i386 CDBOOT 3.65 +boot> +cannot open cd0a:/etc/random.seed: No such file or directory +booting cd0a:/7.5/i386/bsd.rd: 3279379+1442816+4362248+0+417792 [88+160+28]=0x91 +2300 +entry point at 0x20100 + +No dice. I'm gonna try using -hda rather than -drive. No clue the difference. +Works the same. -cpu max instead of qemu64. Works the same. I know this CPU +configuration works because it's the same one from 2024-05-15 that boots +(tested) Windows XP x64. What next to troubleshoot? + +$ qemu-system-x86_64 \ + -M pc -cpu max -m 512M \ + -device rtl8139,netdev=lan \ + -netdev user,id=lan \ + -nographic \ + -hda "$HOME"/Machines/obsd.qcow2 +SeaBIOS (version 1.14.0-2) +iPXE (http://ipxe.org) 00:03.0 CA00 PCI2.10 PnP PMM+1FF8F4C0+1FECF4C0 CA00 +Booting from Hard Disk... +Boot failed: not a bootable disk +Booting from Floppy... +Boot failed: could not read the boot disk +Booting from DVD/CD... +CD-ROM: E0 +Loading /7.5/AMD64/CDBOOT +probing: pc0 com0 mem[639K 510M a20=on] +disk: fd0 hd0+* cd0 +>> OpenBSD/amd64 CDBOOT 3.65 +boot> set tty com0 +switching console to com>> OpenBSD/amd64 CDBOOT 3.65 +boot> boot +0 +cannot open cd0a:/etc/random.seed: No such file or directory +booting cd0a:/7.5/amd64/bsd.rd: 4076463+1688576+3891240+0+708608 [109+464016+317541]=0xaa40e8 +entry point at 0xffffffff81001000 +Copyright (c) 1982, 1986, 1989, 1991, 1993 + The Regents of the University of California. All rights reserved. +Copyright (c) 1995-2024 OpenBSD. All rights reserved. https://www.OpenBSD.org +OpenBSD 7.5 (RAMDISK_CD) #76: Wed Mar 20 15:53:54 MDT 2024 + deraadt@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD + +We got it. I just needed to set the tty to the serial port I was monitoring +with QEMU. Now that I understand the theory I'd really like to get arm64 +emulation working because I imagine it'd be a little easier on my poor CM4. I +foumd a guide on booting OpenBSD/arm64 on QEMU: +<https://www.nechtan.io/articles/openbsd_arm64_qemu.html&rt; +and stripped the weird shit out of it to see if that works. + +$ qemu-system-aarch64 \ + -M virt -cpu cortex-a57 -m 512M \ + -bios "$HOME"/Machines/QEMU_EFI.fd \ + -device rtl8139,netdev=lan + -device virtio-rng-device + -netdev user,id=lan + -nographic + -hda "$HOME"/Machines/obsd.qcow2 +and it works. Hell yeah. + + /blah/2024-06-19.html : decrypting a /g/ riddle @@ -12229,10 +12590,9 @@ WIDTH="88px" blah
 THE WRITER MUST EAT -> patreon.com/trn1ty <-
 
-blah!
-
-a rust, bytes, drugs, nights, bloody kind of life
-get your tetanus shot
+| \    |   | blah!
+|\ | `\|\  | the rantings and ravings
+|/ |(_|| | * of a depraved lunatic
 
 $!NAVIGATION