Second the key-password combo. It keeps the keys you have on the flash drive but adds a password component that thieves would need to figure out as well. Just make sure to pick a good password!
socphoenix
joined 1 year ago
Hahaha yeah…it’s in many ways unfortunate that if you want to play/enjoy this instrument churches are the only option most of the time :/
Definitely worth the watts though!
It is software (grandorgue) that pretends to be a pipe organ (the instrument). In order to run fast enough it needs to load every sound sample into memory to play, as well as usually multiple kinds of sound endings. I play professionally on a "small to mid sized" pipe organ with 1,438 pipes. The one I load for use at home has more than that!
The instrument was from the 1960s and I rebuilt it with a pi pico that you can see here, and you can hear the before (analog sound cards) versus one of the organs I've loaded into it here.
Man my home server IDLES at 76 watts per hour running x86. Now mind you I need the x86 to perform some of the functions I want. This thing works as an NAS, nextcloud, media server, kiwix, security camera (zoneminder), remote desktop (xrdp), runs home assistant, gpu AI upscaling for photos, and finally screeches along running a virtual pipe organ I built that takes 69 GB of RAM to run.
If I could do that with raspberry pi's I would in a heartbeat! the power savings alone would eventually pay for them. If it's doing what you want then don't worry about them. My pi400 works as a remote desktop client and one day I hope more of this stuff will work well on it/a future generation so I can ditch the tower, energy usage, and noise.
I had to use the script twice because I did something stupid the first time but honestly the worst case is you try again!
I’m running arch on my Chromebook I followed the wiki for WiFi then ran the arch install command and set up xfce4. That worked with xbacklight and hot keys setup. I needed a script from mrchromebox to get the speakers working as well but everything else worked out of the box.
It’s 512GB of ssd cache plus 128GB of ram, so for now that’s been enough
You might try adding a cache drive instead. It can help lessen the memory usage zfs needs to maintain speed. My server is spinning rust with an ssd drive attached to the pool as cache.
Command would be “zpool add pool_name cache /dev/sdX” where pool_name is the pool you want the cache on, and /dev/sdX is the empty drive you want to use with it (or partition). Make sure to encrypt this drive before setting this up, my knowledge is zfs doesn’t do that for you.
see here for a bit more information on caching.
T-mobile was doing this in the US but only blocking certain ports when talking to my home server, might try putting it on a non-standard port as well and see if you can access the service then.
Docker on its own won’t think to look at that interface unless you tie it to it. Assuming you want to listen to both interfaces an external watchdog would be the call. You’d set the watchdog to look for iptables issues and then run commands if it went down (ie to restart iptables and then restart your containers).