-
Notifications
You must be signed in to change notification settings - Fork 10
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
Added support file in docs #61
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
## Currently Windows and WSL2 do not support `yast`. | ||
|
||
## Issue with Windows support | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 1.FileSystem -> File System There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think it looks fine now, please check. |
||
|
||
As the config utilities were developed keeping Unix FileSystem in mind, the config files of yast had no support in the Windows File System. | ||
|
||
## Issue with WSL2 support | ||
|
||
Since yast works with targets that require VPN access to fetch results we need to set up a VPN connection in WSL2. However, WSL2 currently does not support VPN. | ||
|
||
## Approach To Solve This | ||
The current approach is to create a Docker image for `yast` to extend its support for multiple platforms. As discussed in #58. |
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.
yast does not support windows and wsl2.
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.
Just to mention, whenever working on docs keep the punctuation and the styles you use consistent. Non-consistent docs show unprofessional behavior. This will significantly decrease your time when working in non-code PRs