marcan
commented
1 month ago The real issue here is that we should wrap bputil/kmutil, ask for the password ourselves, and then do some expect like thing to feed it in. That will clear up the confusion in step2 properly. It's also not entirely trivial though :).
I saw issue #208 and realized that it might not be obvious to everybody what step2.sh actually means when it's asking for “Authorized user”.
(read #208 for more details, that particular user "had no idea that the username and user were different things", and I think that might be more common than you'd think)
i.e. what the installer specifically wants the user to type in is the macOS UNIX username that launched the installer from macOS (="Login user:")
Suggestion:
Show the user's actual UNIX username explicitly in step2.sh ("Login user" will first have to be transferred via the Asahi partition or whatever but this would be amazing customer service)
i.e. instead of these rather vague instructions in step2.sh, record and specify the user's actual exact username ("Login user" from macOS step 1):
Option 2: ...or if that's not possible for some reason, at least add a hint to the "wall of text" instructions (on macOS, shown just before shutting down) that the username you will have to give in step2.sh is (show the current username / "Login user:" that started the installer)