> A terminal is a physical device with a keyboard and screen connected to a computer running various OS types. A tty is the Unix device name for a physical or virtual terminal connection. A shell is the Unix command interpreter. A console is a generic term for a primary i/o device or interface. In unix terms the console is where the boot/startup messages are sent to. After bootup the console effectively becomes a terminal.
A tty can refer to a device name, or a physical terminal.
A terminal can refer to a physical or virtual terminal.
A console could also refer to a physical device, although I'm not aware of it being used in this context.
The problem is that computing is all metaphors. Metaphors leak and once we lose one meaning (enough) we stop clarifying to differentiate. We don't generally need to differentiate between a physical terminal and a virtual terminal, so we don't.
Classic Stack Overflow, willfully ignores the likely intent of the questioner, with pedantic answers which ignore the most common modern usages of the terms. Subtle condescension and authoritative declarations (“a console MUST be a piece of hardware”) which are actually incorrect in modern usage.
Fortunately the top answer doesn't suffer from that issue as far as I can tell. It is much longer and explains both the etymology of the terms and how they are used today.
But it misses the most obvious answer (and most likely where the question originated from): terminal, console, and shell often refer to the same thing.
If one is following a tutorial and it says to “enter this command into your console”, they mean the same as type it in your terminal app or into your shell. The terms are indeed somewhat interchangeable, as a starting point at least for the clearest answer.
Then we can dig into actual differences: the shell is actually an application that runs inside the terminal/console, and you can swap in your favorite shell app; on MacOS, the Console and Terminal apps look similar, but Terminal is what you should use normally, with Console more for debugging system outputs. And so on.
Humor people with practical answers sometimes, for christsake, instead of these agonzing pendantic expositions. Side notes on pseudo-ttys, ioctl, virtual condoles, and control sequences when the OP posted an elementary question?? Yeah, we get it, professor: you are overburdened with information which you must share.
Well, the OP already realized that they often refer to the same thing, and was just curious about the fundamental differences.
> Side notes on pseudo-ttys, ioctl, virtual condoles, and control sequences when the OP posted an elementary question?? Yeah, we get it, professor: you are overburdened with information which you must share.
I don't know if it's elementary but I knew ioctl long before I learned that "tty" stands for teletypewriter. (Top answer: "tty is a strange abbreviation". Me: ha, sure, because if you are curious enough to look up for the abbreviation, the long form itself is pretty much self explanatory).
The answer doesn't feel condescending to me. Similarly, my professor talked to me like that when I was a student and I didn't find that condescending -- it's just a person who knows a particular topic better than me trying to make a gentle introduction.
If someone not only answered my question, but also voluntarily spent another hour telling me all the background stories, I would have nothing but gratitude. Sure, some of those people may not be the nicest person in the world. if you just need a quick answer and be done, you can ask ChatGPT to summarize it.
> But it misses the most obvious answer (and most likely where the question originated from): terminal, console, and shell often refer to the same thing.
Not really. If you ask people at watercooler which _shell_ they are using you are getting 20 minutes conversation about whether zsh is better than fish or vice versa. And if you ask same question about _terminal_ it would be mostly about whether their favorite terminal is GPU accelerated and supports ligatures :)
Watercoolers are devices for dispensing cold (or hot) water from huge plastic bottles in a classic office. People go there to get their hydration fix, say hello to each other, and this ostensibly turns into a longer chat, as everyone keeps procrastinating.
I haven't seen an actual watercooler for the last 10 years, so they're probably becoming less common in tech companies.
One person asks for the specifics of an obscure technical thing. A second person gives a detailed answer with a ton of explanation which thoroughly answers the question. A third person projects their frustration with thorough answers onto this interaction, and laments that nobody gives good answers anymore dagnabit, while missing that their proposed answer is in fact a terrible fit for the question that was asked.
Bonus points for calling someone professor in a derogatory way are cancelled out by (predictably) misspelling chrissakes.
as others have pointed out question poster wanted to know the difference , and the top answer on SO was detailed enough to explain.
there was nothing condescending about at-least the top few answers ( i didnt go through all of them) and ironically by being snarky here , you are being the very thing you accuse SO of
> terminal, console, and shell often refer to the same thing.
often, but not always. if someone tells me they made a terminal program to me it means that it can run without any gui. particularly i can run it in tty and without a windowing system. if someone tells me they made a shell program then its much harder for me to assume the above. actually it probably just means a shell script
Well, if you assume they don't mean GNOME Shell, but something like Bash shell, it's still easy to assume it'll work in a terminal. :-)
A pure shell program (without a TUI library like ncurses) is just a more broad concept, as it would also work outside a terminal in something like Emacs' eshell, but it'll always work in a terminal too.
Is it correct to say that a shell runs inside the terminal? Or that it runs (as any process does) alongside it and happens to have its input and output connected up to the terminal?
I get that you don’t like pedantry, but this seems an important conceptual distinction that I (as someone who doesn’t know much about the internals of OSs) wouldn’t want to get wrong.
> Is it correct to say that a shell runs inside the terminal?
Nope. We use the word "terminal" nowadays to refer to a piece of software that is a terminal emulator. But the thing being emulated is what used to be called a "dumb terminal", which was a piece of hardware that couldn't itself run user software.
"Shell" is the odd man out among these terms; a shell is always a piece of software.
A terminal isn't necessarily a text device. I remember graphics terminals by Tektronix and Apollo. I never saw a blit terminal, but those things existed too.
On SystemV, the console was simply the privileged terminal. My memory is poor, but I seem to recall that (a) there could only be one console, which had to be connected to a specific port; (b) you could only become root if you were on the console.
On some early computers, I believe the term "console" referred to the panel of lights and toggle-switches on the case of the processor. The switches could be used to control memory contents and processor state; so OG wizards were said to be able to e.g. "toggle in the bootloader from the console".
I thought so. My intention was more to subtly correct parent rather than to ask a genuine question. ...although I've learnt a bit more from your reply. Thanks!
MacOS seems to still have something called Console which functions somewhat similarly to what you describe (the panel of lights and toggle-switches, rather than a two-way communication device).
I think of "console" as "point of interaction": it's the prompt that waits for input inside the shell, as well as those blinky lights on old hardware computers.
I don't know, it wasn't always like this. Stack Exchange communities are very different now, I don't think they're the same sites I used to participate in. Coming back to them now resulted in some very negative experiences, people treated me like some worthless spammer whose posts deserve to not only be closed but also literally deleted. It wasn't always like that.
SO is a Q&A based knowledge base. Questions are supposed to be somewhat open-ended prompts that inspire experts to write detailed and informative responses. The OP seems to be an excellent example this.
> Questions are supposed to be somewhat open-ended prompts that inspire experts to write detailed and informative responses.
> open ended
I recently tried asking a question like that. Easy but effective optimization techniques for programming languages. Hell I included an answer myself and was going to add more. The result wasn't pretty. While I was typing up a second answer, the question was downvoted, closed, someone welcomed me to the site and then deleted the comment, the answer I included with the post was downvoted not for being wrong but for "enabling" a bad question, I got told to get out and go blog about it instead and then a few days later the entire thing was deleted like worthless spam.
I had the same experience myself, Stackoverflow isn't going down because of AI which they use as a scapegoat but because the community became more and more toxic to the point of no return and there's no blaming others for that.
Some of the greatest questions on StackOverflow are open ended like that.
I've gotten people to reverse closures before. They closed a Q&A pair I made on the finance site where I explained how I did something specific with the ledger software. Closed, then reopened with a positive score.
Not this time, I guess. I linked that question as an example but it didn't really convince anyone. I was frustrated but eventually I just accepted it, left it alone and went away for a few days.
Came back later to find they had just deleted the question along with the one answer I managed to write. That made me feel like shit. Certainly didn't expect that, especially not from a stack exchange site that's still in beta and thus in need of content.
That's actually a good example of why it happened, and may well be referenced in the meta threads when they talked about it - not only is there no correct answer, these usually acted like clickbait, farming for reputation to gain access to moderation tools.
There is no single correct answer. The answers posted can all be correct and they'll certainly help the people who ask these perennial questions since the question will show up on search results.
> these usually acted like clickbait, farming for reputation to gain access to moderation tools.
The reputation problem is solved by turning it into a community wiki so that votes won't be counted towards reputation. At least it used to be solved that way. Do those still exist? I wrote the posts on mobile and didn't see the usual "turn this into a community wiki" checkbox. I assumed they got rid of it. They've gotten rid of a lot of things over the years, I didn't really keep track.
Nothing you said explains why the post was deleted. They could've closed and locked it to prevent additional answers and voting if it's so problematic. They went the extra mile and completely trashed the answer I wrote. They trashed the efforts of other people who wrote helpful comments with references to additional papers on optimizations. Those comments taught me new stuff. They just deleted all of it. I discovered they had deleted the question because I tried to find those references and couldn't.
I can handle closures, downvotes, rude comments, even insults. Wikipedia style deletionism though? Yeah, that makes me think twice before posting anything there.
A terminal is a device, typically with a screen and keyboard, used to remotely communicate with a computer. Pieces of software that serve this purpose are technically terminal emulators, but in 2024 we just call them terminals because people who use actual terminals, like a VT100 or even an X terminal, are few and far between. So when a Show HN comes along that says "I made a new terminal! It's written in Rust and does this or that" they're not talking about terminals in the traditional sense but pieces of software, a usage of the term I find... urticating.
A shell is a UI to the operating system, used for file management, launching programs, etc. Historically it referred to Unix terminology: the kernel was the bit of the OS that actually performed operations, and the shell was a user friendly wrapper around the kernel's system-call interface. Usages drifted, however, and the shell became called upon to do other things, while the one-to-one mapping between shell commands and system calls drifted and was outsourced to external programs (cp, mv, rm, etc.) But the idea that the shell was your UI into system management persisted. Shells can be graphical; Explorer on Windows and Finder on macOS can be considered shells.
TTY stands for Teletype, an early form of terminal called a teletypewriter. Like a normal typewriter, it printed on paper rather than having a screen. For historical reasons, Unix systems have device nodes called /dev/ttyXX to represent terminal connections.
The console is the main user interface to the system. On old mainframes and minis, it was a dedicated terminal sitting in the room the computer was in and wired directly to it. Other terminals could be located in another room, building, or far away and might communicate with the computer via modem or other telecom link. Some administrative functions, such as installing the OS itself, could only be performed via the console. Today, a typical PC's attached monitor(s), keyboard, and pointing device might be considered the console, and might be abstracted as such through e.g., /dev/console, or at a lower level, NetBSD's wscons(4) kernel driver.
A terminal is a device for remotely accessing a computer. A TTY is a Teletype, a kind of printing terminal; it takes input one character at a time and outputs one character at a time. A shell is the program that reads what commands the user, sitting at his teletype, wants to invoke. A console is the set of toggle switches on the front of your computer you use to load the bootstrap.
Recently I've been wondering if there is a "build your own X" for some of these concepts. For example, there is https://github.com/xyproto/vt100 which seems relatively straightforward (though maybe not "simple") to learn from but are there any resources that would actually teach this stuff?
Precision of language, definitions, and meaning seems to dilute as words gain more widespread usage. Eventually the word becomes a hollow symbol meaning multiple different things to different people, with the intersection between those meanings growing ever narrower.
thats probably true, but sometimes, their meaning can become almost the opposite... take hacker for example... I think that it started as something good.
> take hacker for example... I think that it started as something good.
You just reminded me of one of the earlier uses of “hacker” in popular culture that I’m aware of - They Live (1988) - one of the vagrant guys in the homeless encampment referred to the interference upon the analog TV broadcast as being the work of a hacker:
I remember one of the kids in the film Jurassic Park referring to themselves as a hacker, but this time in a positive light. Not sure if that line was in the original book, or if that was an addition for the movie.
I guess my understanding is that a tty must involve a device driver for an actual piece of hardware. A pty is all software, implemented as a feature of the kernel any application can ask for.
I might be wrong, terminal is a physical/virtual device that output displays or input typing. A TTY/PTY is a mechanism to translate wire protocol bytes (like parse ANSI escape codes). A shell distinguishes bash/zsh/csh. A console is stdin/stdou/stderr
joe armstrong gave a talk where he recommends '4 ancient technologies worth learning', or some such.
one of them is bash, and another is shell (and emacs, and something else).
given that it's joe - i think he knows what he's saying - but it makes no sense with respect to any of these explanations
bash is a shell, it's even in the name: 'Bourne Again Shell'.
But bash is also a programming language. I couldn't find the talk that you're referring to, but Joe might have been referring to
1. 'using the shell' - as in, interacting with your OS through text, learning POSIX commands (which you could be executing with bash) and the mindset you need for shell usage
2. 'using bash' - as in, using bash as a scripting language
What's the difference between 1. and 2. besides interactivity / REPL? "Using the shell" means inputting the shell language into the interpreter; "using the shell as a scripting language" includes POSIX commands, and the mindset needed is the same in both use cases, no? The beauty of shell is in that exact crossover.
https://www.reddit.com/r/programming/comments/41u5hw/comment...
> A terminal is a physical device with a keyboard and screen connected to a computer running various OS types. A tty is the Unix device name for a physical or virtual terminal connection. A shell is the Unix command interpreter. A console is a generic term for a primary i/o device or interface. In unix terms the console is where the boot/startup messages are sent to. After bootup the console effectively becomes a terminal.