-
Notifications
You must be signed in to change notification settings - Fork 13.8k
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
Foundations / Installation Overview: Preliminary WSL2 Introduction #25402
Conversation
Include preliminary introduction to WSL2.
Whoops, sorry @xandora, just noticing this is in draft. Would you like a reviewer assigned yet or do you have a bit more to do before it's ready for review? |
It's very very draft, I just wanted a PR to point people to from the beta channel to kick off the collaboration. |
Lessons that need to be touched:
At some point, it'll need to be communicated how to deal with filesystem difference and in particular, how to move files from Windows to WSL2's filesystem. This could be introduced when it's installed. I might think it's best to be put here in Links and Images, which is the first time learners would actually need to use this. The rules and bot commands (hosted in other repos) will have to be updated as well. Probably want to have it so everything is rolled out together. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good so far, I'm excited for this. Let me know if I can help by testing anything
I am going to remove the 'needs triage' label from this one to get it off of the list since it's still in draft... feel free to start pinging maintainers and/or add that label back when you're ready for a review here. |
@xandora I think all the relevant lessons have now been updated, so this should be ready for review once the merge conflicts are resolved |
I have gone through my previous review and left the ones unresolved that seem to be missing from the file now. Feel free to resolve those if they have become obsolete. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left a bit more general feedback, mostly involving the installation lesson and style/formatting.
Good job everyone!
Co-authored-by: Manon <[email protected]>
Co-authored-by: Manon <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nothing to review from my side.
This is going to be a huge step forward in supporting windows; kudos to everyone contributing 🚀 🔥
|
||
2. Next, download [this image](https://unsplash.com/photos/Mv9hjnEUHR4/download?force=true&w=640). | ||
|
||
3. Right click on the new download at the bottom of the chrome window and select "Show in folder". |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a blocker, but could be good to include instructions if a user doesn't have this enabled. "Alternatively, open the "Customize and control Google Chrome" kebab menu and select the "Downloads" item. This will show all of your downloads, each with its own "Show in folder" button."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Forgot to reply to this, but this is ✅ Done
|
||
4. Drag the file from your downloads folder to VSCode's file browser into your new `images` directory. | ||
|
||
Dragging files from Windows into the VSCode file browser prevents the `Zone.Identifier` files from being copied over. From now on, any time you need to copy pictures or other downloaded files like this into WSL, you can do it in this way. If you ever accidentally copy these `Zone.Identifier` files into WSL, you can safely delete them without any issue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel like we should still include some alternative instructions to drag and drop, even it means warning that copy pasting or whatever other way may result in a (harmless) duplicate file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a small amount of dragging and dropping with the alternative:
- Using your Ubuntu terminal, navigate to the folder you want to copy the image to (
cd ~/odin-links-and-images
for example) - Type
cp <space>
- Drag the dog.jpg image from a Windows Explorer window and drop it onto the terminal window, it should appear as
"/mnt/c/users/username/Downloads/dog.jpg"
- Type
<space> .
to tellcp
that you want to copy the file to your current working directory- The full command will look something like
cp "/mnt/c/users/username/Downloads/dog.jpg" .
- The full command will look something like
- Hit to complete the command, and use
ls
to confirm the file now exists
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The alternative alternative is to just do this:
- Copy the file in Windows Explorer
- In Windows Explorer, navigate to Linux > > /home//etc
- Paste the file in that folder
This does get the :Zone.Identifier
file, but doesn't use drag 'n drop
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe the solution is as simple as updating the verbiage to "Either drag and drop or copy and paste..." or something
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added the extra explanation by @xandora , which I think should be enough. If we see that lots of learners on Discord run into issues at this step we can always add extra instructions
@xandora despite the number of comments above 🎉 🔥 🚀 on this content! 😆 |
Will try to get to the comments either today or tomorrow |
Co-authored-by: Eric Olkowski <[email protected]>
Okay, so that was a lie, but I think I should have gotten all your comments @thatblindgeye |
Pokes @thatblindgeye |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a reply to convo above, but I don't think it's a blocker at the moment. "Drag and drop this file..." may be synonymous to "copy and paste..." to users.
I think it should be okay to merge at this point. Hopefully, we have gotten every major issue fixed, and if anything minor pops up we can always fix it later |
**DO NOT MERGE:** Depends on TheOdinProject/curriculum/pull/25402 ## Because - We're moving to support WSL2 ## This PR - Updates the rules file to refer to WSL as a supported OS ## Pull Request Requirements <!-- Replace the whitespace between the square brackets with an 'x', e.g. [x]. After you create the PR, they will become checkboxes that you can click on. --> - [x] I have thoroughly read and understand [The Odin Project Contributing Guide](https://github.com/TheOdinProject/theodinproject/blob/main/CONTRIBUTING.md) - [x] The title of this PR follows the `keyword: brief description of change` format, using one of the following keywords: - `Feature` - adds new or amends existing user-facing behavior - `Chore` - changes that have no user-facing value, refactors, dependency bumps, etc - `Fix` - bug fixes - [x] The `Because` section summarizes the reason for this PR - [x] The `This PR` section has a bullet point list describing the changes in this PR
Include preliminary introduction to WSL2.
Because
It's about time we include WSL2 as an option for learners to work their way through the curriculum.
This PR
Issue
Additional Information
Pull Request Requirements
location of change: brief description of change
format, e.g.Intro to HTML and CSS lesson: Fix link text
Because
section summarizes the reason for this PRThis PR
section has a bullet point list describing the changes in this PRIssue
section