I am using the AUTOMATIC1111 stable-diffusion distribution, and you can install modules to that. Some modules can be installed and updated from inside of the program, while others cannot. Those other modules have to be updated by doing a git pull. This is not a big job, but it can be made even smaller with a very small shell script.
I wanted a nice way to simply see whatever statistics I could gather from my GPU — ye olde PNY XLR8 1070 slightly-pre-overclocked model, which I bought used and which has been surprisingly solid so far — and for some reason the information I want to see isn't in the default output from the nvidia-smi command included with the nvidia driver, and I don't get anything in lm-sensors. Noodling around a bit led me to the idea of using the --query-gpu option, which lets you pull any specific information you want, as long as you are willing to deal with it in CSV format. I was, and here we are.
Without getting [too] technical (and probably operating "above my pay grade") the ZFS ZIL is a place where synchronous writes are done, and you can move this to a separate zpool, which is called a SLOG. One SLOG can store the ZIL for multiple zpools. While most writes by most applications are asynchronous, some are not, and file metadata writes are synchronous. Putting the ZIL for a HDD (or even an array) on a SSD lets your zpool provide the IOPS performance of your SLOG, while also avoiding fragmentation and reducing seeks through ordered writes.
If you have a very old nvidia card, you will want to use the FOSS nvidia driver (nouveau) as it is likely the only thing that will work for you. But realistically, if you have nvidia graphics on your system, you will want to use the binary driver. This is a quick guide to that. The nvidia driver is in the non-free repo, so make sure you have that added to your sources.list. Then you can do the following various things (as root, or sudo as necessary)
Anyone who has more than a passing familiarity with Linux audio knows about the pulseaudio daemon, and its long history of causing problems with Linux audio in the name of solving them. What it gave us was per-application volume control, but what it took away was reliability. The good news is that there is now a superior replacement for pulseaudio which also replaces JACK in the bargain, called pipewire.
I have recently made the switch as a Linux user from LUKS, LVM and ext4 to ZFS, ZFS, and ZFS. I started it with Ubuntu, which conveniently offered me an encrypted root on zfs option which worked very well for me in general. However, every time I had to interface with systemd it felt like a chore, when what I really wanted was the old school UNIX feel I got from Slackware. And now I've converted to Devuan 4 "Chimaera" on ZFS, which is based on Debian 11 "Bullseye", which is as close to that as I'm willing to get given the amount of work I want to do. In the process, I've had to mount my old zfs filesystems on my new system gracefully, and this is how I went about that.
This is based on a number of documents, beginning with OpenZFS Debian Bullseye Root on ZFS. There are some notable changes. View the original document and follow along:
One of my favorite features of modern filesystems is the sparse file, where "empty" portions of files are unallocated, so they don't consume any space. This allows oversubscription of disk blocks, so long as you never actually complete fill all of the files at once. But one common problem of sparse files is that they tend to grow, and there is often no way to solve this problem in place. But there is, with ZFS.
This site, my glorified blog, started out on Drupal 4. It wasn't until Drupal 8 that there was finally a single official way to handle putting media into nodes, with a media reference field and a media embed filter. Between then and now I used first the venerable img_assist and then the image_filter module, both of which fell by the wayside after D7. I replaced them both using php custom filters, but php in the database is now deprecated for security reasons.
...as soon as I can get hosting... because my host is still stuck on PHP 7.4. This means that I'm still stuck with D7. But this blog is about converting my site from D7 to D9. I was able to preserve everything, it seems, down to text formats — but all of them were refusing to display because they had references to missing filters, so it made it look like none of my content was present.