Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone

Today it's awk(1)

Uncategorized
1 1 5

Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 0 Votes
    1 Posts
    5 Views
    Today's #FreeSoftwareAdvent entry is my podcatcher, castget(1). I've used several CLI podcatchers over the years, changing mostly because hpodder (my then-favorite) became deprecated and dropped out of repos, so I had to find a replacement.Configuration is a simple INI-style file, it allows me to post-process files (certain ones I cut off the 7-minutes of advertising at the beginning, customize ID3/ID3v2 tags), and give them a naming-convention that works for how I listen.It runs nightly from cron(8) downloading to my queue directory-tree, emailing me the resulting output, and saves its state in files that can be fairly easily tracked in version-control (annoyingly it doesn't sort them, so every run mangles them, but a little processing with vim makes quick work of them, meaning the resulting diff output is just the new podcasts and a top-level timestamp change, not a complete remunging of the file). About every 3–4GB of queued-up files, I've usually reached the ones on my player/phone, delete those, and replace them with the fresh queue. It does mean that news podcasts are largely worthless because there could be a 3–4wk lag between when the episode releases and I eventually catch it in my player.It's simple, it works, and it plays well with the rest of my ecosystem. I like it.
  • 0 Votes
    1 Posts
    4 Views
    Following on the heels of ssh(1) yesterday, today's #FreeSoftwareAdvent is rsync(1).It's one of the key elements in my podcast listening (more on that to come later this month), where my podcatcher pulls down podcasts into a backlog tree structure, and I rsync the whole thing to my phone for listening. It also undergirds my blog deployment, building in Nikola (still gotta find some time to switch that to my custom Makefile driven build process) and then rsync'ing the output/ tree up to my web-server.And last night our teen wanted our family photo website content's pictures for a school project, so I was able to rsync the latest copy of them to a backup USB drive that he could browse offline.It's reliable and does a particular job (keeping two directory trees in sync) very well. Yes, ZFS send/receive is more efficient if both sides support it and they're whole datasets, but that's not always the case.Also, since I use bash as my shell, the "^" substitution makes it easy to issue something like$ rsync -n -avr $SRC $DESTand if it looks good, use$ ^-nto remove the dry-run flag and run it for real.
  • 0 Votes
    1 Posts
    5 Views
    Today in #FreeSoftwareAdvent it's ZFS. It gives me• all in one volume management (no volume-groups and logical volumes and manually resizing partitions on those logical volumes with a dozen different commands, no playing the "oof, need more space on partition A and have too much free space on partition B, back up all the files, nuke both, shuffle partition-sizes/locations, restore the files" dance)• transparent file compression• transparent volume encryption• fast and effectively free snapshots and clones (you start paying the cost if they diverge or deleting files that remain in a snapshot, but that's to be expected)• same-disk redundancy with copies=2 to help prevent against bitrot, and multi-disk redundancy with effectively zero effort• the CoW means no need for fsck(8) horribly slowing my boots or finding orphaned fragments of files and shunting them into a lost+found/ directory (my biggest frustration with OpenBSD's FFS2) in the event of an abrupt power loss• efficient send/receive (beats rsync hands down in terms of speed)• fine-grained quota/reservation control• utilities make scripting easy with output-formatting options• cross-OS support in a way that very few other filesystems provide (other than FAT 😆)I'm sure there are additional reasons that didn't percolate to the top of my brain, but it's just so much more pleasant than any other disk management I've done on any OS.
  • 0 Votes
    1 Posts
    3 Views
    Though a bit niche, my #FreeSoftwareAdvent today is ed(1). As the goofball behind @ed1conf, I certainly play it up, but I certainly use it more than the average Unix/BSD/Linux user.A while ago I wrote up list of reasons¹ why one might use ed, and some are more obscure/improbable reasons (though I've encountered all of them in that post), there are a couple of those that drive me back to ed regularly:• I can still see the output of previous commands on the screen while I edit, where a full-screen editor would obscure that output that I need to incorporate in my edit• it's just darn fast for a quick edit, changing a variable name or adding/removing an entry in a list, etc. No startup costs for a honkin' huge $VISUAL with dozens of plugins and language-server processes and GUI rendering• very usable on low-bandwith/high-latency connections like I sometimes get when I remote into machines (less of a problem now, but I still experience sessions where I'll SSH in, invoke ed, make the change, write & quit, and exit the shell, in a couple seconds, while the screen repaints things oh-so-slowly• and most importantly, there's quality geek-cred for using it in front of others 😆⸻¹ https://blog.thechases.com/posts/cli/why-ed1/