While working on a project, I was wondering if I could make it very difficult to execute a script. I'm creating bash functions in separate files, and they're replacing scripts that used to be executed directly. I am removing execute permissions, but some well-meaning future self might try and "fix" them by re-adding those permissions. Could I stop them from being executed in other ways?

• terminal
• bash

I work from home, and my wife commutes. Every day, in the afternoon, I find myself constantly leaning over and parting the shades to check and see if I hear her driving up the driveway, or if I'm just hearing random road noise. It's a silly problem, with an even sillier technical solution.

• bash

I tend to do a lot of things with some terrible, terrible bash scripts. Backups, listening to music, creating temporary virtual machines... and also, listening through my podcast backlog. This last one gets pretty complicated, and while looking into how to manage it, I discovered a bash script technique that surprised me.

• terminal
• bash

I run a 12TB RAID 5 array comprised of three 6TB hard drives. My RAID setup is defined in software, not hardware - which has served me well, as it has been migrated between three installs and two separate sets of server hardware. The raw drives have been added to a MDADM software RAID array, which is encrypted with LUKS, and partitions are managed by LVM.

• linux

I've been messing around with a markdown editor called Formiko. It provides a side-by-side markdown editor, much like Jezra's Markdowner. Why was I fooling around with Formiko if I already had a working solution?

• markdown
• linux
• troubleshooting
• wayland