Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

step2: Wrap kmutil/bputil to improve UX #224

Open
rxhfcy opened this issue Oct 14, 2023 · 1 comment
Open

step2: Wrap kmutil/bputil to improve UX #224

rxhfcy opened this issue Oct 14, 2023 · 1 comment

Comments

@rxhfcy
Copy link

rxhfcy commented Oct 14, 2023

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:")

Collecting system information...
...
  Login user: (username)

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):

98  echo "Please enter your macOS credentials (for the macOS that you"
99  echo "used to run the first step of the installation)."

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)

@marcan
Copy link
Member

marcan commented Jun 1, 2024

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 :).

@marcan marcan changed the title Explicitly show the user what "Authorized user:" means (which username) step2: Wrap kmutil/bputil to improve UX Jun 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants