Fix Windows File Systems not being mounted on first start when using the Installer #79
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I was able to consistently reproduce this when WSL was started with Windows Terminal Preview, can confirm that the first commit ( fix "cd: /root: Permission denied" ) is good. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add a
/bin/mountbinary to the installer, so that WSL can correctly mount the file systems/etc/fstabis not required, but an error appears if it is not presentWhen the shell is started in
/root, syschdemd now silently changes to the default user's home directory, in order to prevent an error message from appearing. This happens, when WSL is started in a directory, that is not available in the guest fsCloses #72