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

No echo when running command from Crsh #53

Open
nyh opened this issue May 25, 2014 · 0 comments
Open

No echo when running command from Crsh #53

nyh opened this issue May 25, 2014 · 0 comments

Comments

@nyh
Copy link
Contributor

nyh commented May 25, 2014

Crsh switches the terminal to raw mode (not exactly, but close enough) when reading the command line, so it gets the input after each character, and does it own echo.
However, just before we run a command, we need to switch back to cooked mode, so that the command we run can behave as Unix programs expect, to be run in cooked mode (and get echo and a line discipline).

I remember we got this working correctly, but apparently it longer is.
If you run

$ make image=memcached.none,mgmt.full
$ scripts/run.py
[/]% run memcached.so -u root

You see memcached.so runs without echo enabled (if you type anything, you don't see what you type). OSv is not hung at this point, it's just not echoing characters.

To see that echo is working outside crsh, run the same memcached directly without crsh:

$ make image=memcached
$ scripts/run.py

and see how the input characters are echoed.

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

1 participant