If I do this; wouldn't it also prevent a user from being able to reattach the usb to a windows pc to modify or copy their oneBash? I intentionally made the partition with oneBash a windows partition, to ensure that windows users could interact with it.
I have no problem having an image that supports both usb and ssd; I thought it was best to direct users to use a USB key instead of an ssd in order to save users ~$30. I will ensure that I implement ssd support in the next version, as if you think it is important; others probably do as well.
I will get to this eventually. Thanks for offer to build a playbook, I may take you up on that later. I have some ideas I want to implement which may make this unnecessary. I am currently only doing this in my freetime; soon I will go crypto fulltime (for the second time) and really get to work on this and other projects.
It would prevent them from being able to mount the Windows partition and edit directly. I'd suggest you consider making the onebash file available by itself for download. People can edit on Windows/Mac/etc, and then use scp to copy it to the mining rig.
Setup would be - burn image to whatever. Once the machine starts - scp onebash, and go.
BTW - I only used SSD's because I have a bunch of 30G ones laying around, and I'm impatient and like faster boot times.