-
Notifications
You must be signed in to change notification settings - Fork 183
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
remote/client: fallback to telnet when microcom is not available #1412
Conversation
See also this: I was going to take a look at implementing something internal...but if you have time/inclintation to do it, PLMK |
This workaround is not really invasive, so I'd be inclined to merge it. @Emantor @Bastian-Krause? |
Hi again, I implemented a simple internal terminal here: |
Please squash the fix commit and rebase, this should also fix the DCO error and this should be ready to merge 👍 |
Done. |
microcom is generally not available on rpm based distributions[1], making it hard to setup labgrid client on them. [1] https://repology.org/project/microcom/versions Signed-off-by: Nick Cao <[email protected]> [[email protected]: rebased, added CHANGES.rst entry] Signed-off-by: Rouven Czerwinski <[email protected]>
microcom is generally not available on rpm based distributions[1], making it hard to setup labgrid client on them.
[1] https://repology.org/project/microcom/versions
Description
Checklist
Tested the telnet code path in a fedora container.