carcus

+1
I fondly remember having the bootloader on a floppy to dual boot my own machine due to some limitation about where Linux lived on my hard disk, but honestly it was probably more of a knowledge limitation at the time!

First shell was on a Debian 1.x machine in my friend’s living room since they had broadband.

That’s fair, I had thought op had mentioned they didn’t read fiction, not that they didn’t read at all. Maybe I missed some nuance in the comments, thanks for pointing it out if I did. For all I knew they could be reading Foucault. Enjoyable read regardless, I wouldn’t be discouraged.

Haven’t seen this one mentioned, but The Three-Body Problem by Liu Cixin might work. I don’t believe there’s a lot of first person, but it’s an interesting read.

Love a tracker! I saw people running dirtywave M8 headless on a steam deck. Needs a teensy connected and some packages/config, nearly tried it myself but got a preorder for a M8 instead.

Depending on what method of suspend you are employing, it could be due to lack of sufficient swap space. That’s a common problem.

Without more info this is a good best guess. However, Instead of the graphics card I would suspect an undersized swap space to support hibernation.

Learned about the importance of trailing slashes in rsync by using the -delete flag.

Ableton’s Push 3 standalone runs Linux too. Same gripe about their DAW as well.

Happy to help. As I have it configured, my local network is set to prefer direct play, so any transcoding gets done from connections that traverse the boundary of my network. If you don’t live with your parents this would likely apply.

Transcoding may also occur when you have subtitled content and I believe for certain audio formats, but the transcoding would be limited to the audio track.

No worries. I got a beelink S12, non-pro model with 8G RAM and 256G SSD. It was on sale for about $150 USD. Fit my use case, but maybe not yours, although you might be surprised. Perhaps those extra plex share users won’t be concurrently transcoding?

The drives are all USB, the portable type that requires no power source. Like you, I don’t need much. I have ~12T across 3, with a small hub that could provide more ports in a pinch. This model I believe also provides a SATA slot for a 2.5” drive, but I haven’t used it. All of these drives were previously connected to a rpi 3B+, haha!

The drive shares are done via samba and also syncthing. I have no need for a unified share via mergerfs, but I did take a look at this site for some ideas. I’m the type that rolls all their own services rather than using an NAS based distro. Everything is in an ansible playbook that pushes out my configs and containers.

Edit: I should make it clear the NAS is for other systems to access the drives. Drives are directly connected via USB. All my services are contained in this single host (media/backup/microservices/etc). My Pi’s are now clustered for a k3s lab for non critical exploration.

I’m a bit of a minimalist who designs for my current use with a little room to grow. I don’t find much value in “future proofing” as I’ve never had much success in accomplishing that.

You may want to consider a mini PC. That was my upgrade after torturing my raspberry pi for many years. I landed here after agonizing over building the perfect NAS media server. Still very low on power consumption, but the compute power per dollar is great these days. All this in only a slightly larger form factor over the pi. I brought over the drives from the pi setup and was up and running for a very low cost. The workload transferred from the pi (plex, NAS, backups, many microservices/containers) leaves my system extremely bored where the pi would be begging for mercy.

I don’t do a lot of transcoding, so I’m no expert here, but looking at the documentation I believe you would want a passmark score of 2000 per each 1080p transcode, so 8000+ for your 4+ streams, not including overhead for other processes.

I’ve had to do forensics on a rogue change. In finding when and who actually changed the file, mtime can help narrow it down when compared with wtmp.