4 ms·
Still seems like a fundamental misunderstanding of what a terminal is for. I SSH into any number of boxes every day, be it on my RaspberryPi, client machines in
by audleman 10y ago
Still seems like a fundamental misunderstanding of what a terminal is for. I SSH into any number of boxes every day, be it on my RaspberryPi, client machines in AWS, crappy hosting providers, etc. The standard bash terminal is there on all of them, which can not be said of any project like this.
- nilliams 10y agoThis is a 'terminal emulator' (client). So what you ssh into is irrelevant and Bash etc. are also irrelevant. This is a client you could ssh from (and use whatever shell you like, locally and remotely).
- LukeShu 10y agoYour comment is a fundamental misunderstanding of what a terminal is for. Bash is not a terminal, it is a shell. You interact with the shell through the terminal. Old-school terminals were physical devices that had their own keyboard and CRT display, and were connected to the computer via a serial port. Modern "terminals" are actually terminal emulators (software that emulates the older hardware) that display the emulated terminal display on your screen. That might be your kernel's /dev/tty1 which displays the text by directly writing to the graphics card. Or, it might be a user-space application that displays it as a window in a graphics system; such as PuTTY[1], Terminal.app, iTerm, XTerm, gnome-terminal, or one of these projects. [1] PuTTY is not just a terminal emulator, it is also an SSH client, among other things.