But surely you need a program to direct your attention to those programs, otherwise how would you know what you’re supposed to be doing? You need to have another power hungry program running that uses a full center worth of processing power to… *checks notes* …do what your google now homepage used to do.

A sacrifice to Dükt, may he forgive our transgression for not using his most holy gift.

At least at work it’s ITs problem if shit goes awry.

What is fairy bread?

*Ecosias “fairy bread”*

What the fuck. Surely this is a mass traumatic response to being a former penal colony.

I played Mercenaries a bunch and had a blast loading up as many machine guns as I could on a relatively agile mech and just fully unloading on some big ass Atlas’ cockpit in order to salvage it.

It wasn’t exactly a fantastic strategy, but a great way to get a beast of a mech.

The nice thing about keeping most of my stuff on spinning rust is the throughput on the drives are just about the same as the network.

Less options and it expects user input, so when you update and there’s a changelog or warning, it shows it to you and you can read it. It doesn’t continue because it thinks you’re there reading it. The options and output are subject to change, so you don’t want it in a script. Apt-get will always have the same options and expected output for automation purposes.

Well, music is kind of a team sport, I’d be pissed if one of the percussionists could never hit the damn triangle at the right time.

I’m sometimes disappointed that I live in blue NM. There’s no politician I can hassle, and Stansbury is even arranging protests, so who am I supposed to yell at when she’s there in the crowd?

My favorite is how 15th St just boings off of Colfax (15th ave)

Blocky artifacts are the result of poor bitrates. In streaming services it’s due to over compressing the stream, which is why you see it when part of a scene is still or during dark scenes. It’s due to the service cheaping out and sending UHD video at 720p bitrates.

I’ve done that click and drag many times. Nothing worse than accidentally dragging a folder designated with pseudo random numbers into another pseudo random numbered folder, and not knowing if you actually dragged it into a folder, or missed and did nothing

This seems to only be true in conservative States.

I try keep my data drives and boot drives separate on my servers, I make sure I can rebuild the server relatively easily so no matter what happens I can get back up and running. In my research on LVMs I wasn’t seeing anything saying you could just move the drives to a new setup, that you had to export and import first. In the case of a suddenly dead boot drive, I wouldn’t be able to do that. I did see some steps for backing up an LVMs metadata and recovering from that, so I might be sure I do that at some point, but another user said that modern distros should be able to scan for LVMs without issue, which is not what I found in my quick test in my setup. So I’ll be checking that out in a more modern setup to double check.

From what I was reading, recovering from corrupted metadata is not something I want to do. I’d rather not use LVM if that’s what’s required if I can’t just move the drives to a new server, as nice as it would be to resize filesystems on a whim.

I did not find just moving the drives to work. There were some other issues that I came across that might have a part to play in it, I made the lvm and filesystem on an RPI5 running OMV and moved it to a rock3c running OMV from an armbian install. Turns out there’s a pagefile size mismatch between the two that prevented mounting the btrfs filesystem. But I still wasn’t able to get the rock3c to recognize the VG or that there were new PVs attached without exporting first. So perhaps the armbian install isn’t modern enough to automatically recognize it.

I didn’t expect learning new things about btrfs to be the outcome of this little experiment, but I guess that’s just how things work.

That’s kind of what I figured, my biggest concern at this point would be how difficult it is to move the lvm volume to a different device. It seems pretty straightforward if you have a working setup, but from what I’m seeing in my research is silence if your device (server, etc.) dies and you need to move those volumes to another. I’m finding guides on either recovering from corruption or lost metadata, or transferring from one working device to another. Nothing I can find about importing a fully functional lvm to a new device if it hasn’t been exported.

I’ll be able to do that later today, so I guess I’ll see what happens if I do. Better to try it out now when it isn’t critical.

I try to keep lossless on my server for the fact that new algorithms come out all the time. I don’t want to be stuck with a 160k mp3 when a better algorithm comes out or if I need to stream just a little lower than that. I’d rather have lossless quality that can be converted at any time to whatever I need, even though I mostly have it set to 160k for listening if I’m streaming away from home. My work internet and cell service can get really terrible, and being able to buffer 10 songs when I get a few minutes of service is a godsend while not getting stuck with low quality, several times converted files, or keeping multiple bitrate versions of the same song.

Kind of, but not really. There are specific requirements in order to charge, not hard to meet on grid, but can be difficult in a homemade setup

Framework was and is certainly high on my list, but I’d rather go in a used direction and I do have concerns about them sponsoring hyprland and omarchy, and I haven’t seen anything about them backing down on their statements.

If I were to categorize what I consider most important as far as upgradability goes, it would be the following:

1. Storage - Drives fail, full stop. It needs to be replaceable. Storage can also be a backup to ram, so if that isn’t replaceable something needs to be. My experience with a 32gb nonreplaceable storage laptop has soured my entirely on non-replaceable storage.

2. Ram - Ram can fail and as technology proceeds, ram tends to be the most expendable resource as technology progresses. So as time goes on, what you started with just won’t cut it in the future. I don’t see this changing anytime soon, so it either needs to be upgradable or way overboard in capacity and to a lesser degree speed.

3. Secondary components (wifi, bluetooth, etc.) - I honestly don’t mind replacing these components with a usb dongle, but it sure would be nice to replace the internal components and leave USB ports free.

4. Graphics - I’m not a laptop gamer, I don’t see it as the place for it. While there are some processes that would benefit from a better GPU, I feel like mobile CPUs cover that aspect very well.

5. CPU/motherboard - A replaceable cpu is a rarity to find in a laptop, and processing power/watt doesn’t seem to have a huge difference within generations which is probably my most important factor in a laptop. Sockets change so often and chipsets aren’t often compatible with newer chips that I don’t much see the point if the motherboard isn’t replaceable. It would be cool to have a replaceable motherboard, but considering how fine I am with older technology, I think even those would still be outdated by the time I start considering that anyway.

I think it was 24-40, not 18. Soo yeah.