I’m not too familiar with the setup of etcher on OSX, but what does the following shell command print?
file /Applications/balenaEtcher.app/Contents/MacOS/balenaEtcher
file /Applications/balenaEtcher.app/Contents/MacOS/balenaEtcher
/Applications/balenaEtcher.app/Contents/MacOS/balenaEtcher: Mach-O 64-bit executable x86_64
That’s strange, I’d definitely expect the sudo call to work. Can you execute that file without sudo?
For example:
/Applications/balenaEtcher.app/Contents/MacOS/balenaEtcher
Yes, it was strange, and it was my mistake. I saved balenaEtcher 1.5.57 under a different name alongside v1.5.51, then when I tossed 1.5.51 I didn’t rename 1.5.57 back to basic balenaEtcher, so there was nothing there for the CL to call. It does work now, using sudo.
What I still don’t understand (since I now have nothing to flash) is if the CL call launches something different from the GUI call.
I believe the GUI entry just executes the same binary that you would run on the CLI. In terms of the difference between running with sudo or not, it means that etcher does not have to escalate itself to perform the writing.
Got it - thanks.