That actually makes a lot of sense. I never even second guessed how tedious all the parsing is. But then, as others have said here, as soon as the task at hand reaches a level of complexity beyond grepping, piping and so on I just very naturally move to Python.
On a different note, there are ways to teach bash json. I recall seeing a hacker conference talk on it some time ago, but didn’t pay close attention.
Mh, it probably depends a lot where you’re coming from. I don’t need Powershell or have a reason to learn it in my daily work, and I mostly use WSL to access Linux shells everywhere else. And on top of that, I don’t understand why Powershell needs a completely different command set to basically every other shell. It’s a biased take, but I have not had an interaction with Powershell that I liked, nor have I seen a feature that made me want to look into it more.
What’s the killer feature, would you say? Care giving me the fanboy-pitch?
edit. Oh and I forgot, the tab completion in Powershell is so incredibly dumb. I never ever in my life want to cycle through all items in a path, and much less have it be case insensitive. Come to think of it, this might be the origin of most of my disdain. ;)
WSL has changed the game pretty significantly, don’t you agree? It’s not perfect, but allows me to stay firm in my resolve never to learn powershell.
I have done a similar thing in the past, but to flash firmware onto any device with a certain USB descriptor that gets plugged in. It was a mess of USB hubs and cables, but it worked.
What I did was write a udev rule that checks for the vendor and product id of a newly plugged in device and calls a script when there’s a match. The script then performs the flashing and logs the output.
In your case:
ddthe source USB to a file (make sure the partition you’re dding is smalled than any target driveEdit. Did this on a rpi3