am stuck on the [not entirely unpleasant] horns of a dilemma.
since receiving my various new goodies t'other day [not only, but importantly including, two new #SSDs; 2 TB & 240 GB], i've been having a bit of a self-inflicted time of it here, atop my swaying gum tree. whilst my main, original, SSD continues to hold entirely lovely #ArchLinux #Plasma & #SparkyLinux #Cinnamon systems, for yonks now i've been getting more & more fascinated by the new kids on the block, being Plasma immutable / atomic systems:
- #KDELinux
- #Kinoite
- #Kalpa
The new 2TB is for my new #VirtualMachines playground, replacing the recently deceased 2TB HDD. The new 240GB one is to allow me to play around IRL [not just virtually anymore] with those atomics. So over the last coupla days i have been bouncing twixt multiple installations, trying to decide. Today, just before making this post, the latest installed one therein is KDELinux again. It's running quite nicely, & is a bit of a joy to use, but, being only Alpha, has some important problems, incl.
- whilst i've gotten its #Flatpaks working for app pkgs, it cannot actually do any System Updates atm, neither in Discover GUI, nor in Konsole. My dilemma is that i cannot tell if this is my local problem, or an upstream server fault. If it's the latter then i'm happy to just wait it out, knowing they'll fix it. However if it's my local problem then i could wait til the cows come home & it'll never be right. Dilemma!
- earlier RAW images d/i from the Project Banana site have had broken #Distrobox, & some have had working DB. My one sadly has a broken DB, which is a showstopper for me unless i can get a good system update that fixes it [but, see preceding point].
What to do, what to do? Wait it out, or bounce on to another reinstallation of Kinoite... or Kalpa? 🤨🤔🤷
#dropbearinterwebz #dropbearpooterising #firstworldproblems