gridbugs

Tonight I ran into an issue where when a rust program panics on my FreeBSD laptop, the stacktrace doesn’t contain code locations, and instead shows <unknown> on every line: $ RUST_BACKTRACE=full cargo run --bin gpt-fat-disk-image-create -- -l README.md -d…

Digging through an old hard drive I found a game I forgot I made.

I bought some new SSDs to install FreeBSD on a media server I’m setting up.

Today I updated the permalinks for these daily posts to be based on title of the post rather than the date.

A few months ago I swore off the nodejs and ruby version managers, claiming that the language ports should suffice.

Here’s a little experiment I did to familiarise myself with ZFS on FreeBSD 12.1.

Recently I changed the server config for this site such that upon navigating to “gridbugs.org”, you are forwarded to “www.gridbugs.org”.

The other night, by a string of coincidences, I had an experience where every hard drive I tried to use would fail.

Last night I tried to set up a media server and managed to break just about everything I touched.

“GPT” stands for “GUID Partition Table”, and “GUID” stands for “Globally-Unique IDentifier”.

My first attempt at implementing disk image creation feels messy.

I’m slowly getting there.

I updated all the posts on this site that previously linked to files.gridbugs.org or games.gridbugs.org to point to my itch.io page instead.

Four of the five games I’ve made in the 7DRL game jam can be played in a browser, and all are available for download on my itch.io page, but in most cases I’d neglected to take advantage of the feature of itch that lets browser version of the game be host…

After I accidentally let all my AWS TLS certs expire, attempting to play any games on games.gridbugs.org (such as Skeleton Crew) results in a scary warning about security risks ahead.

FAT32 defines a section named FSInfo at the start of the partition where the number of free clusters, and the index of the next free clusters, are stored.

In a recent update, Windows saw fit to mess with my EFI (boot) partition in such a way that my Windows/Linux dual-boot setup no longer functioned.

During the peak of covid in NSW I stopped bouldering.

A few months ago I switched this site’s web hosting from AWS to nearlyfreespeech.

I look forward to the non-standard clues in DA’s cryptic crossword in the SMH on Fridays.

I’m making a program that takes a list of files as an argument and creates a GPT/FAT32 disk image that contains them.

I realised several months ago that I don’t feel imposter syndrome at my current job.

The “FSInfo” sector is the second sector of a FAT32-formatted partition.

I’ve started a git repository for storing my favourite cryptic crossword clues.

A few weeks ago I saw an eel in the Moore Park pond, floating partially out of the water.

Or at least the 10 years since I started using Vim?

My last few posts have been general because I haven’t had time to make any meaningful progress on personal projects due to spending almost every waking hour at work.

I don’t believe the term “functional” is a meaningful description of a programming language.

I think among engineers there is a tendency to overvalue those ideas whose complexity can serve as a kind of proof of intellect.

The FAT filesystem and GPT partition table both set aside part of the partition and disk for storing a backup of header information.

In the field of image processing, convolution refers to an operation which takes an image (a 2d array of pixels) and computes a new image of the same dimensions by considering each pixel of the input image, and a relatively small number of nearby pixels,…

In my initial design for meap, the Parser trait contained this method which extracts typed values from an untyped low-level parser output: fn parse_low_level( self, ll: &mut low_level::LowLevelParserOutput, ) -> Result<Self::Item, Box<dyn error::E…

Now that meap is feature complete, I’ve started adding it to some personal projects as a replacement for my previous command-line argument parser - simon.

In a conversation with some coworkers a few days ago I said something that sounded clever.

My command-line parsing library - meap - can now generate help messages such as this: $ cargo run --example macro -- -h Finished dev [unoptimized + debuginfo] target(s) in 0.02s Running `target/debug/examples/macro -h` Usage: target/debug/example…

Muscle memory is weird. ... => roglkpl!

After 5 years of gradually degrading service (as expected of any phone, sadly), my LG Nexus 5 succumbed to a stuck power button, as has been the fate of the Nexus 5 of everyone I know who owned one.

I renamed my work-in-progress command-line argument parsing library from “args_af” to “meap”.

I added a quality-of-life macro to args_af to make it easier to specify arguments: struct Args { optional_int: Option<i32>, string: String, flag: bool, } impl Args { fn parse() -> Self { (args_af::args_map!

Today I got args_af to the point that it can parse command line arguments.

For today’s post I originally set out writing an explanation of the concept of Applicative Functors.

A natural way to approach the problem of command-line argument parsing is to split it into two parts.

A few years ago I made simon - a rust library for parsing command-line arguments.

When I first started working on mini_gpt, the first thing I made was a parser for the disk image’s Master Boot Record (MBR).

Last weekend I played the first chapter of Epistory - Typing Chronicles.

Since I’m retraining my hands to type in qwerty rather than dvorak, I figure I’ll use this as a chance to kick some bad habits in Vim - my text editor of choice.

Today I completed the tools for reading and listing files from a gpt/fat disk image.

Here are two complications of switching to qwerty that I’m dealing with.

For the past 10 years I’ve used a dvorak keyboard, but I’m currently trying to switch back to qwerty.

In the original version of my disk image tool I read the entire image file into memory once before processing the image.