Treating your personal website like a garden you tend continuously, not as a finished construction, but rather cultivated, authentic fragmented of web. #blog #Hugo #IndieWeb

I’m not sure when it happened, but for some time now, `apt search` has been using a pager (probably `less`) to display results. Whatever the reasoning behind this change, it just irritates me. After some digging, I found a few ways to deal with it. ## Don’t use `apt search`# A suboptimal solution is to rely on the older `apt-cache` command for searching, as it doesn’t use a pager. So, instead of calling: ~/2026/01/disable-the-pager-for-apt-search/ apt search kitty I could do this: ~/2026/01/disable-the-pager-for-apt-search/ apt-cache search kitty It works, but it requires a few more characters to type. I write enough time over the day writing, to waste time on typing extra characters, so that’s a no for me 😉 ## Disable with an environment variable# Another option I found was to use an environment variable: ~/2026/01/disable-the-pager-for-apt-search/ PAGER=cat apt search kitty But come on! It’s even more to write. ## Reconfigure `apt` to disable the pager permanently# This one took me a while to find, as it’s not easy to find docs for that. You can create a configuration file to disable the pager for `apt` entirely. This is the best way to do it, as it disables the pager without affecting other features like colorized output. ~/2026/01/disable-the-pager-for-apt-search/ sudo tee /etc/apt/apt.conf.d/99-no-pager > /dev/null << EOF Binary::apt::Pager "false"; EOF Now, `apt search` will print directly to the terminal, just like it used to (and in color!). * * * Enjoyed this post?

Fix ZSH ‘illegal modifier’ errors with Git Conventional Commits by disabling the NO_BANG_HIST option.

Configure Windows to use UTC for the hardware clock when dual-booting with Linux, avoiding time synchronization issues and maintaining Linux defaults.

Snakes in SuitsUnderstanding and Surviving the Psychopaths in Your Office Authors: Paul Babiak, Robert D. Hare I read the Polish translation titled “Psychopaci w pracy: Jak ich rozpoznać i jak sobie z...

Reflections and practical tips from 20 years using Getting Things Done, plus a short workshop plan for leaders who want actionable routines.

Learn how to add an llms.txt file to your Hugo blog to make it more visible to AI agents and improve Generative Engine Optimization (GEO).

I was preparing to move data from my old PC to the new one. Just wanted to backup one of my NVMe drives but when I tried standard `dd`, it failed: Calling standard dd root@box:~# dd if=/dev/nvme1n1 of=/storage/backup/disk.img obs=1M dd: error reading '/dev/nvme1n1': Input/output error ... It was my second drive, which I do not care that much but still wanted to make a backup so I could restore what’s possible on new system. I started looking for option to force `dd` to skip problematic bytes/blocks - whatever possible - and that’s how I found `ddrescue`1. I heard about it, but I didn’t had occasion to use it before. Calling ddrescue root@box:~# ddrescue -f -n /dev/nvme1n1 /storage/backup/file.img /storage/backup/file.log GNU ddrescue 1.27 Press Ctrl-C to interrupt ipos: 1024 GB, non-trimmed: 233472 B, current rate: 33996 kB/s opos: 1024 GB, non-scraped: 0 B, average rate: 258 MB/s non-tried: 92602 kB, bad-sector: 0 B, error rate: 16384 B/s rescued: 1024 GB, bad areas: 0, run time: 1h 6m 4s pct rescued: 99.99%, read errors: 9, remaining time: 1s time since last successful read: 0s Copying non-tried blocks... Pass 1 (forwards) ipos: 856031 kB, non-trimmed: 385024 B, current rate: 10264 kB/s opos: 856031 kB, non-scraped: 0 B, average rate: 258 MB/s non-tried: 6619 kB, bad-sector: 0 B, error rate: 24576 B/s rescued: 1024 GB, bad areas: 0, run time: 1h 6m 6s pct rescued: 99.99%, read errors: 13, remaining time: 1s time since last successful read: 0s Copying non-tried blocks... Pass 2 (backwards) ipos: 917962 kB, non-trimmed: 471040 B, current rate: 60645 kB/s opos: 917962 kB, non-scraped: 0 B, average rate: 258 MB/s non-tried: 393216 B, bad-sector: 0 B, error rate: 106 kB/s rescued: 1024 GB, bad areas: 0, run time: 1h 6m 7s pct rescued: 99.99%, read errors: 15, remaining time: 1s time since last successful read: 0s Copying non-tried blocks... Pass 4 (backwards) ipos: 1024 GB, non-trimmed: 577536 B, current rate: 60645 kB/s opos: 1024 GB, non-scraped: 0 B, average rate: 258 MB/s non-tried: 0 B, bad-sector: 0 B, error rate: 106 kB/s rescued: 1024 GB, bad areas: 0, run time: 1h 6m 7s pct rescued: 99.99%, read errors: 19, remaining time: 1s time since last successful read: 0s Copying non-tried blocks... Pass 5 (forwards) ipos: 1024 GB, non-trimmed: 0 B, current rate: 81920 B/s opos: 1024 GB, non-scraped: 233472 B, average rate: 258 MB/s non-tried: 0 B, bad-sector: 16384 B, error rate: 5632 B/s rescued: 1024 GB, bad areas: 32, run time: 1h 6m 8s pct rescued: 99.99%, read errors: 51, remaining time: 1s time since last successful read: n/a Trimming failed blocks... (forwards) Finished Now I had image. It wasn’t fully correct because of failed reads, but at least I didn’t need to restart `dd` multiple times. I was able to fix filesystem with `fsck`, then I had to reinstall few packages to recreate broken files and that’s it. * * * Enjoyed? * * * 1. https://www.gnu.org/software/ddrescue/ external link ↩︎