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
  1. Home
  2. Categories
  3. Uncategorized
  4. Today in #FreeSoftwareAdvent #newsraft #RSS

Today in #FreeSoftwareAdvent #newsraft #RSS

Uncategorized
1 1 0
Log in to reply

Feed RSS
Today in #FreeSoftwareAdvent #newsraft #RSS

Gli ultimi otto messaggi ricevuti dalla Federazione
@pierobosio@soc.bosio.info
Post suggeriti
  • gumnos@mastodon.bsd.cafeundefined

    Today's #FreeSoftwareAdvent entry is my podcatcher, castget(1).

    Uncategorized freesoftwareadvent
    1
    0 Votes
    1 Posts
    0 Views
    gumnos@mastodon.bsd.cafeundefined
    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.
  • gumnos@mastodon.bsd.cafeundefined

    Today in #FreeSoftwareAdvent it's the venerable ssh(1)/sshd(8)

    Uncategorized freesoftwareadvent
    1
    0 Votes
    1 Posts
    3 Views
    gumnos@mastodon.bsd.cafeundefined
    Today in #FreeSoftwareAdvent it's the venerable ssh(1)/sshd(8)While I grew up in an age where telnet(1) was my only option, the ssh folks made it a pretty drop-in replacement for the sorts of things I did with telnet, so switching was easy.With the exception of when I'm rebooting or our ISP is having issues, I almost always have at least one SSH connection open and likely more than one connection to other hosts. Even in the "security" of our LAN in the house, I still SSH between machines rather than use unencrypted connections for transfer.I love being able to run things remotely and use them locally, such as$ ssh me@remote dmesg | xsel -ibto put the remote machine's dmesg output on my system clipboard or$ tar czvf - /path/to/data | ssh me@remote 'cd /destination/path ; tar xzf -'to transfer a directory tree to a remote machine.It generally has sensible defaults, allows me to force key-based authentication rather than username+password auth.It allows me to limit $DAYJOB customers to SFTP-only access within their designated chroot directories, insulating them from each other.I use it to tunnel into work and forward my RDP VM's screen so I can access it locally with rdesktop(1)So many delightful little uses.Definitely worth reading @mwl's SSH book to learn more: https://mwl.io/archives/3126
  • gumnos@mastodon.bsd.cafeundefined

    Today in #FreeSoftwareAdvent, it's pf(4)

    Uncategorized freesoftwareadvent
    1
    0 Votes
    1 Posts
    2 Views
    gumnos@mastodon.bsd.cafeundefined
    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.
  • gumnos@mastodon.bsd.cafeundefined

    Though a bit niche, my #FreeSoftwareAdvent today is ed(1).

    Uncategorized freesoftwareadvent
    1
    0 Votes
    1 Posts
    2 Views
    gumnos@mastodon.bsd.cafeundefined
    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/