Heel yaw 👊

Same as you would on MacOS :

• ditch the .deb package because it’s the wrong tool for the job here.
• Squashfs image with encryption
• Set keyring entries and a wrapper script to manage lock/unlock. If you already know the hardware platform of all users, this can even be improved upon

I have no idea why someone would be using Debian packages to distribute something like this though, if that’s the question. Absolutely not going to work well.

Well that engineer is fired.

I thought the last couple moves were the nail in the coffin, but this might be it 🤣

You’ll still be running into frequent issues if you go with R-V, so be warned.

That being said, the Framework R-V board only comes for the 13" format, so you can buy a cheap Framework 13 refurb from their store (fully warranted and everything), and swap the board out for the R-V for $200.

There are other R-V laptops out there, but I think the build quality is nowhere near the Framework, AND if you feel like it sucks, just swap that board back with the one it shipped with.

If you just want the machine to do something only WHEN it detects the TV, that’s a bit different. You want an HDMI or DP switcher. You can just make a tiny listener for DBUS events that launches BPM when it detects the TV coming online.

Simple bash script set to run once your DE is loaded would do it. Detect the TV with xrandr or equivalent, then start Steam in BPM. If not, do nothing.

Yet none of this will reduce Fuckerberg’s cash pile. We need to take that back.

This sounds like some RFK “facts” bullshit. I assume the number is not actually zero, but will wait for the math.

Clop Slop

Also, possibly an STI? “They got the Clop Slop!”

Edit: Actually, I think just “Clop” works

MacOS, phones, off-brand handhelds that run SteamOS…that’s the goal.

It’s not going to be effortless. That’s not really the goal. Anything that uses Google Play Services is going to be a problem still as the underlying service layer just mocks out those API calls a la Waydroid. They’re working more on the FEX stuff from what I’ve seen in the repos.

Having the disks connected externally is the same as having them connected internally

No, it 1000% is not, especially in the case of USB that I used. Even in the way Linux handles everything as a file and target, it is vastly different.

No RAID solution I know of would lose the array on a power outage

Hardware RAID enclosures have batteries on the disk controllers for this very reason. We aren’t talking about those though, we’re talking about software RAID on JBOD, which wouldn’t have those sanity protections. Here’s some random blog explaining deeper.

Honestly I don’t see how interrupt handling would be any different between internally or externally connected devives, except for different buses/protocols handling it differently intrinsicly

See above

Maybe I’m too spolied by using ZFS, but again I don’t think this would actually be a problem

That’s a filesystem solution to a hardware problem, so yes, probably a bit spoiled there, or at least it’s skewing your understanding of what RAID is and how it works. One of the reasons ZFS exists, actually. It’s nice to have nice things though.

Well…don’t overspeak. There WILL eventually be something better, and then people will complain about that as well 🤣

Also software. Literally in the description and options.

There are very few use cases for hardware controllers anymore, and they are on SAN controllers at a massive scale. Every single device you point me to at under $50k is going to be software.

Just wanted to clarify so you understand.

Software. They’re all software. They run Linux, actually.

Link me to a single hardware controlled disk array that you’re considering.

The main issue is statefullness of the host.

Say you’re on a laptop, and you get an external JBOD box without any hosted controller. You use that laptop to setup a RAID1 array on 2 disks, and go about your business. Few weeks in you’re in the middle of some editing of video or whatever, and you have a power outage.

That RAID array is assuredly damaged or dead. Your host machine being the controller in the middle of a write when the entire array dissapears is going to give up quickly, and the cached data in flux to write is gone. You miiight be able to recover the array if you’re lucky, but whatever you’re working on is gone.

A number of diff5scenariis where this may happen exist without a power outage, but the problem is the target not being able to manage its own interrupt, and you have two different states in two different devices that won’t match. It’s toast.

There’s a few things at work here:

1. Not much “hardware” RAID anymore because offloading works just fine and doesn’t draw excessive resources.
2. It sounds like you want to just take your existing disks and pop them into something else, which won’t work.
3. You shouldn’t be running RAID over any external connections for a number of reasons if the coordinator (your machine) is hosting it. I can go deeper into that if you want.

You want a self-contained NAS that manages its own RAID and disks. I would honestly just get a diskless unit and start clean. You’ll be better off in the long run.

Why would I care about swaying your opinion? Nobody here responding to you is invested in YOUR opinion on the matter, or cares what you think about it. They are simply correcting your misinformed attitude about some things from what I can see.

If anything they’re concerned you’re running around in the world with misguided opinion, and potentially misinforming others.