Posts by gumnos@mastodon.bsd.cafe
(DIR) Post #B0Yi7rBJruVloYZkDQ by gumnos@mastodon.bsd.cafe
2025-11-24T04:07:35Z
0 likes, 0 repeats
@tomjennings while I don't aspire to purchase one, I wanted to send my compliments on the lovely work you've done making the fZ80!
(DIR) Post #B0ocrhEzfZ7n6o7ywS by gumnos@mastodon.bsd.cafe
2025-12-01T20:23:07Z
1 likes, 0 repeats
@claudiom ah, music/keyboarding rather than retrotech š
(DIR) Post #B0sodwISs3p1penVTc by gumnos@mastodon.bsd.cafe
2025-12-03T14:34:29Z
1 likes, 0 repeats
Today's #FreeSoftwareAdvent entry: ledger(1) & hledger(1)I primarily use ledger use for my #plaintextaccounting purposesĀ¹ but try to mostly keep my data-files in a form that hledger can process them too.Getting started involved a crash-course in accounting terms, but the use of positive/negative numbers (rather than "debits" and "credits" which always bugged me; though both have ways of specifying that output should be in credit/debit format) eased the transition.While it started a little tedious, a few helper-scripts and shell-functions simplified adding new common entries and gave me lazy access to common reports.I still struggle a little bit with closing the books (I though I'd figured it out, and documented itĀ², but had some hiccups so I'll need to revisit my documentation in January)But it's been incredibly helpful to see and track our household net worth, spot trends, keep tabs on gift-card balances that would otherwise get forgotten, track invoices sent to clients, and it simplifies balancing the checkbook monthly.āø»Ā¹ http://plaintextaccounting.org/Ā² https://blog.thechases.com/posts/closing-out-the-books-in-ledger/
(DIR) Post #B0soe4C1VtQIJzqTY0 by gumnos@mastodon.bsd.cafe
2025-12-03T15:07:21Z
0 likes, 0 repeats
I supposed I should have linked to the projects too š:https://ledger-cli.org/https://hledger.org/
(DIR) Post #B0svXBcuB0TN1p5MQq by gumnos@mastodon.bsd.cafe
2025-12-03T22:07:16Z
0 likes, 0 repeats
Ah, modern techology.Me: I'd like to connect to another accountPlaid: Great, which one, and provide credentialsMe: Here ya goPlaid: Looks good, they sent an OTP, please provide itMe: Here ya goPlaid: Something went wrong. Try again?Me: SurePlaid: Great, which account, and provide credentialsMe: Here ya goPlaid: Looks good, they sent an OTP, please provide itMe: Here ya go (2nd OTP)Plaid: Something went wrong. Try again?Me: NoPlaid: Are you sure you want to cancel and lose your progress?š¤¦āāļø
(DIR) Post #B0ubF3y0J5ONICxG5Y by gumnos@mastodon.bsd.cafe
2025-12-04T14:00:49Z
1 likes, 1 repeats
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/
(DIR) Post #B0wtw9gJ7gDoxXILAW by gumnos@mastodon.bsd.cafe
2025-12-05T14:35:52Z
1 likes, 1 repeats
Today's follow-up #FreeSoftwareAdvent entry is vi/vim.Which I use depends on the situation. Classic vi/nvi tends to be lighter weight and start faster, while vim offers extra features that I find particularly useful). I usually just type `vi` which gets me `vi` on OpenBSD, `nvi` on FreeBSD, and `vim` (or `vim-tiny`) on most flavors of Linux. If I specifically want vim features, I'll invoke it as such directly.I could go on for ages about favorite features, but a select few:ā¢ the ability to keep my hands on the home row and not use a mouse is helpful for preventing RSI symptomsā¢ it's a languageĀ¹ of editing, involving counts, verbs/commands, and objects/motions, so I can express my editing *intent* and then use the period command to re-issue that same editing *intent*ā¢ the :global or :substitute commands can make massive-yet-precise edits across huge filesā¢ the :*do commands extend that power across multiple files, allowing me to precisely edit millions of lines across thousands of files with targeted precisionā¢ it's ubiquitousāeven as some Linux distros have started removing ed(1) from the base installs , relegating it to packages, I can always type `vi` on any Unix-like/POSIX system and be editing with a powerful editor. And with builds for Windows and my phone, I can use it everywhere. No need to install anythingā¢ they work just fine over a SSH connection without a GUI, and use minimal resources so they work even on that old hardware from the 90s.āø»Ā¹ https://gist.github.com/nifl/1178878
(DIR) Post #B17yuLCvvzxidb4Kem by gumnos@mastodon.bsd.cafe
2025-12-09T15:42:07Z
1 likes, 1 repeats
Going a bit off the beaten path for #FreeSoftwareAdvent, today I get to appreciate HaikuOSĀ¹. While it has some issues (mostly keyboard-mapping) that prevent me from using it as the main OS on my writerdeck netbook, it is AMAZING in how well it uses resources. That little underpowered Atom processor with its 2G of RAM just flies. It boots in a fraction of the time of anything else (other than DOS) that I've installed on the hardware. The GUI and all the applications are delightfully snappy.So please join me in sending a little praise toward the @haiku project for all the wonderful work they do!āø»Ā¹ https://www.haiku-os.org/
(DIR) Post #B1Ee5TxezUpI2c7EWW by gumnos@mastodon.bsd.cafe
2025-12-13T22:26:11Z
1 likes, 0 repeats
TIL: $HOSTALIASES in FreeBSDApparently you can set the $HOSTALIASES environment variable in FreeBSD (and maybe some Linuxen? but not OpenBSD AFAICT) to point to an alternate hosts file (instead of the default /etc/hosts) for re-mapping particular hosts. This would let you do something like$ HOSTALIASES=$HOME/hosts.txt myprogand any name-resolution that myprog(1) does will first consult the ~/hosts.txt file.https://man.freebsd.org/cgi/man.cgi?query=hostname&sektion=7
(DIR) Post #B1F2G7ZYyAc0gnRywC by gumnos@mastodon.bsd.cafe
2025-12-14T14:07:20Z
1 likes, 1 repeats
Today in #FreeSoftwareAdvent, it's pf(4)Having lived through several iterations of firewall management tools on Linux (and FreeBSD offers both IPFW, IPFilter, and pf in the base system), I've come appreciate the simplicity and declarative nature of pf.conf for my firewall management.The only downside is the quirky syntax of pfctl(8) but I do like being able to run my rules through it to sanity-check them from vi/ed with:w !pfctl -nvf -before installing them.
(DIR) Post #B1WMG3LgF6BypNH8K0 by gumnos@mastodon.bsd.cafe
2025-12-20T14:12:33Z
0 likes, 1 repeats
Today's #FreeSoftwareAdvent appreciation is for some of the Free Software languages that bring me both joy and income: Python & GolangI've used Python at $DAYJOB since version 2.3 (it got woefully stuck at 2.4 for WAAAAY too long, and finally switched to 3.x some time in the last 2ā3 years) and it simplified so many automation tasks there. I've used dozens of programming languages in my life for various tasks, and the hard part is rarely *writing* the code, but rather *reading* the code. And I find it a LOT easier to come back and read old Python code than just about any other language.Meanwhile, Golang saved my bacon on a short-term contracting project where TB of (simple) CSV files needed to be processed, cross-referenced. Being able to spin up a pool of multithreading Go processes, have built in locking and hash-map structures, and operate on raw input buffers of bytes shaved a 3-day manual process down to about an hour involving running a single command. I find it pretty readable too, feeling a bit like C while ditching some of the most cumbersome aspects.
(DIR) Post #B1mYuoaWKoFGtsmLTc by gumnos@mastodon.bsd.cafe
2025-10-03T12:02:10Z
1 likes, 0 repeats
@chesheer I'll take Vim's smart-but-deterministic behavior over LLMs' random output any day š
(DIR) Post #B1zA4h3FEsAuceJ636 by gumnos@mastodon.bsd.cafe
2026-01-05T19:38:02Z
1 likes, 2 repeats
pilfered from around the web
(DIR) Post #B23es81iBe7qmhEa6y by gumnos@mastodon.bsd.cafe
2026-01-07T15:03:18Z
0 likes, 1 repeats
@jpmens I have a similar supperpower of being able to spot errors in my own texts after I've pushed Ā«sendĀ»š
(DIR) Post #B2DZdzC1g1MR8w5wiu by gumnos@mastodon.bsd.cafe
2026-01-12T17:49:48Z
1 likes, 3 repeats
Ah, another day full of Microsoft joy.Months ago: $DAYJOB disabled access to standard IMAP/SMTP clients, limiting only to approved UA IDs via OAUTH2. So no mutt/neomutt, no OfflineImap/mbsync, no Claws, and no Thunderbird. Just the Outlook thick-client and the web-client. Fine, so I'll use the thick-client.A month or three ago: some upgrade happened breaking the Outlook thick client. Their only options were upgrading the OS on the VM (to support the latest Outlook thick-client) or using the web interface. They didn't upgrade the VM, so I'm stuck with the unbearable web interface.Today: I go to log into the webmail interface, and the SSO server web interface is down preventing me from reading or sending *any* email. Including what would have been cached offline by any of the above clients.Meanwhile, my personal IMAP/SMTP server? still provides access from any CLI, GUI, sync-utility, or web client I set up. My MUA allows for offline access, so at least I can compose replies and queue them up if things go offline. Sigh.I guess it's time to find something other than work to do.
(DIR) Post #B2UGaANbGoGEyRqJqC by gumnos@mastodon.bsd.cafe
2026-01-20T20:19:18Z
0 likes, 0 repeats
@justine I think that also has an alias `pkg prime-list` by defaultTo be fair, I never remember either, so I have an entry for it in my mega notes.txt file saving me from having to reconstruct the command from man-pages. If you need it, the OpenBSD counterpart is `pkg_info -m` or `pkg_info -mz` (depending on how loose you want the naming)
(DIR) Post #B2UHbIqJOErFSvNVzc by gumnos@mastodon.bsd.cafe
2026-01-20T20:30:56Z
0 likes, 0 repeats
@justine here's hoping your memory is better than mine (or that you dump it in your corresponding notes.txt outrigger-brain š)
(DIR) Post #B2UUYQb5OxP03DDSOu by gumnos@mastodon.bsd.cafe
2026-01-20T15:16:24Z
1 likes, 0 repeats
@jpmens A never-ending battle š
(DIR) Post #B2YC6xlbSlYSH1jGTo by gumnos@mastodon.bsd.cafe
2026-01-22T17:19:01Z
0 likes, 0 repeats
@h3artbl33d @ParadeGrotesque Okay, which one is incredibly dense/stupid: me or the quote?I thought qcow/qcow2 were disk-image formats and hadā¦umā¦nothing to do with cryptography?
(DIR) Post #B2c49G7iA8cYmeUf5M by gumnos@mastodon.bsd.cafe
2026-01-24T14:35:52Z
0 likes, 0 repeats
@justine As @nafmo notes, the old loose objects will be present but benign until GC happens. Normal usage should automatically gc the bare repo in the fullness of time, but you could theoretically force it.If you are comfortable with destroying and recreating the bare repo (I do that plenty when testing things) then both will eventually quiesce into roughly the same state. The only concern would be if you had pushed branches to the bare repo, then deleted them locally, but then want to re-clone them locally. Deleting the repo would lose those branches that you don't already have locally. But it doesn't sound like that's the case, so not a major concern.