John Goerzen @jgoerzen@floss.social

2/ Not needed for this, but even better would be something that could multiplex input from multiple sources in some sort of chunked format, interleaving as needed, and split them back out again on the other end.

Does anyone know of a multi-file streaming archiving tool that can accept input from pipes, FIFOs, or commands? #tar can do what I want for output with -O, but not on input, because each file's header contains a size, which of course wouldn't be known for streaming input. Must be able to separate files back out again on the other end.

The closest I've come is #uuencode, which can concatenate output and #uudecode will identify the individual components - but of course it has a space penalty.

The v1 that I have been using for the last 6 months has the Blue keyswitches. Mmmm clicky. However I ordered brown ones for this one, on the grounds that they will be less obtrusive for use while on the phone.

Just ordered my SECOND #UltimateHackingKeyboard . I may have a #mechanicalkeyboard weakness... or maybe I care about the health of my hands and wrists? (yeah, that must be it!)

#Ergonomic mechanical #keyboards seem to be rare. I tried two others before picking the UHK; it's the perfect blend of easy to get used to plus ergo. The v2 now has hotswap keyswitches, which is fantastic.

Remote directory tree comparison, optionally #asynchronous and #airgapped with #NNCP or #UUCP: https://changelog.complete.org/archives/10198-remote-directory-tree-comparison-optionally-asynchronous-and-airgapped I take a look at several tools that can create summaries of filesystems, including permissions, sizes, and even file #hashes. Useful for verification of #backups and can be optionally used #offline.

If you ever wonder if the police treat Trump's goons more gently than #peaceful #protest ers, look at https://www.cnn.com/2021/01/11/us/dc-police-previous-protests-capitol/index.html

The good, bad, and scary of the banning of Donald Trump, and how #decentralization makes it all better - with a shout out to #mastodon and the #fediverse. https://changelog.complete.org/archives/10193-the-good-bad-and-scary-of-the-banning-of-donald-trump-and-how-decentralization-makes-it-all-better

@TinyDevOps Great to see you here! Welcome to the Fediverse!

This is how tyrants go: alone.

https://changelog.complete.org/archives/10191-this-is-how-tyrants-go-alone

There is #hope today.

#ZFS 10/ OK, an addendum. With crypto, you can even do incremental #backups (with zfs send) without ever mounting the filesystem or knowing its decryption keys - the output stream will have encrypted data, but zfs send just looks at changed blocks so you're good! Also since ZFS is copy-on-write it has better properties for SSDs that have issues with sudden power loss than most filesystems.

And to conclude, 9/ reasons I don't use #ZFS.

Although I use it on every machine I can, it is somewhat RAM hungry, so I don't run it on my #RaspberryPi machines or other very old hardware. Though I now have an 8GB Pi on hand that I intend to try it with.

It always makes me nervous, though. Running without protection against silent data corruption feels... unsafe 🙂

Why I use #ZFS

8/ More stable than #btrfs. Although btrfs provides many of these benefits - plus the theoretical benefit of more flexibility with rearranging data - every time I have tried btrfs, I have run into serious bugs. Some of them have been corrected, but not all. https://btrfs.wiki.kernel.org/index.php/Status gives the btrfs status. It still has pathologies with many snapshots, I believe still also with databases, though I think hardlinks have been fixed.

Why I use #ZFS

7/ More flexible volume management (in most but not all ways) than #LVM. By integrating the filesystem and the volume manager, resizing a filesystem is just adjusting its filesystem quota.

However, it is difficult to remove devices from a ZFS zpool once set up.

Why I use #ZFS

6/ zvols. You can do all of this with chunks that are presented as block devices, too. Want to back up that Windows virtual machine running under KVM or Virtualbox? Create /dev/zvol/foo with ZFS, attach it to the VM, and you can snapshot and backup and clone just as you would with a filesystem.

Why I use #ZFS

5/ Built-in #compression with fast algorithms (lz4 and now zstd). In many cases the compression is fast enough that the reduced I/O results in a performance gain.