PartialVolume

@cyberm8 good to know, I'll do a rebuild and release as soon as I can.

See #263 Specifically https://github.com/PartialVolume/shredos.x86_64/issues/263#issuecomment-2234461146

This might be a good idea from a developers perspective for ease of testing but from a users perspective being restricted to a official release of nwipe is safer in...

>Ahhh understood, valid points, what do you think about something in the buildroot to switch between stable, and master like in many buildroot-based projects? Yes, that could work. From the...

>It's also possible to lock the submodule for a specific commit in the nwipe.mk file, e.g. the releae commit. I'm not clear on what you mean here. If I understand...

Ok, if you can implement the switch, so the dev can switch between the two methods I can then test your RC4 branch at the same time on some older...

Nice work!, I'll test that out and get back you.

Quick question. can you explain why the commit number is needed? Would it generally point to the last commit in the branch?

Needs debugging, there's a couple of path errors re patching ../../ should be used instead of ../../../ for the sub module section re patch file locations? File permissions 003-nwipe-banner-patch.sh needs...

Thanks, Looks good, it will save us some time messing about calculating hashes. I'll give it a try over the next couple of days and then commit.