4 ms·
But you can't move the shell across layers. It's needed where it is. The point of the shell is that it's how you issue commands to the computer. You (or GP) wa
by thaumasiotes 5y ago
But you can't move the shell across layers. It's needed where it is.
The point of the shell is that it's how you issue commands to the computer. You (or GP) want to make the commands independent of the shell. OK. How do you issue your new shell-agnostic commands? How is the computer supposed to understand them?
For that to happen, you'll need to implement a shell in the exact place where you just removed the first one.
- strager 5y agoA shell has three parts: * the command editor * the command interpreter/parser * the fork()/exec() calls I think you're talking about the fork()/exec() calls. I'm primarily talking about the command editor.
- thaumasiotes 5y agoOK, so on the server we have a protoshell running which accepts commands and makes system calls. (I don't think your three-part listing makes sense: commands are the input to the shell, and system calls are the output. But you can't separate them -- without input, what output are you producing?) And now, on the client, we have a command editor running which accepts keystrokes and produces commands. But the client runs on a different machine. It doesn't know what commands the protoshell over on the server can accept. How does it know what commands to produce?
- viraptor 5y agoI implemented that as a joke, but basically it can work like this: https://github.com/viraptor/libremotec https://github.com/viraptor/libremotec The app captures syscalls working on FDs and forwards those to the remote side. You could do that in much more clever ways. You can also do it in hacky simple ways like for example ansible does, by just running each command remotely.