Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Difference between console and Terminal. Post 302507991 by Corona688 on Friday 25th of March 2011 10:48:23 AM
Old 03-25-2011
Quote:
Originally Posted by theKbStockpiler
I see these terms used all the time with hardly any distinction between the two.
Isn't one, really. Terminal's probably the more "technically correct" term but they both make sense.
Quote:
I could only get emacs to open in console so I was also wondering what are the common applications to use in console.Smilie
Anything that demands user interaction and isn't a graphical program naturally has to be in a terminal, since a terminal is the way to get interactive information from the user. Editors(nano, vi, emacs) need a terminal if you're not using a graphical version of them, and login systems in particular (su, sudo, ssh, scp, sftp) demand a terminal of one sort or another.

Shells can use terminals, when available, to give you an interactive prompt, but are quite capable of running noninteractively and without a terminal too, when running shell scripts.

I'd also point out a small but important distinction; quite a few utilities couldn't care less whether you run them in a terminal, a GUI, or no environment at all. They just do their job and don't even worry about where they are or why. Unless the command interacts with you somehow, you can be relatively sure it falls into this category... Commands like cp and mv and awk and a blizzard of other common utilities fall into that category.

So it's not really a different "kind" of program, just programs using the resources available to them in different ways.

Last edited by Corona688; 03-25-2011 at 12:00 PM..
This User Gave Thanks to Corona688 For This Post:
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

console terminal

if I am on "host13" and I rlogin to "host14" using root, is there any way to open up a console window on "host14" so that it will appear for that particular user sitting there at the time (1 Reply)
Discussion started by: AMisledDrummer
1 Replies

2. UNIX for Dummies Questions & Answers

Terminal vs console

What's the difference between a terminal and a console in Sun 5.5 CDE? Gives the option to open a console or terminal window, was wondering what the diff is? (1 Reply)
Discussion started by: kymberm
1 Replies

3. Programming

what difference between "terminal" and "console"

1 . Thank you for reading the post first. 2 . what difference between "terminal" and "console" (1 Reply)
Discussion started by: chenhao_no1
1 Replies

4. AIX

Difference between tty and console devices ?

Hi, What is the diference between these two ? thanks Vilius (3 Replies)
Discussion started by: vilius
3 Replies

5. UNIX for Dummies Questions & Answers

Difference between console and ttys

Sometimes when I open up the terminal (like just now) it says Last login: Wed Jun 17 07:29:25 on console sometimes it says ttys (like when I exit and open a new window/tab). What's the difference? and is something fishy going on? (6 Replies)
Discussion started by: Straitsfan
6 Replies

6. Fedora

console vs terminal ???

Hello sir, I was using the FEDORA 10.I saw both Console and terminal here.Can u please brief me about the differences between these two.....:confused: (3 Replies)
Discussion started by: nsharath
3 Replies

7. UNIX for Dummies Questions & Answers

Difference between system console and ILOM .

HI Guru's Can any one explain me the difference between a system console and a ILOM (SC). Thanks in Advance. RK :) (4 Replies)
Discussion started by: rama krishna
4 Replies

8. UNIX for Advanced & Expert Users

Console vs terminal

What is the difference between a console and terminal? When you hit ctrl+alt+f2 from the gui are you going into a console or terminal? (1 Reply)
Discussion started by: cokedude
1 Replies

9. Shell Programming and Scripting

How to start a shell script in a terminal console from graphic environment?

Hello. Normally when you double click on the file name, the shell script start in background. If you want to see what is going on, you must open a terminal console and start the shell within the terminal. Is it possible to start directly a shell script in a terminal console from the file... (0 Replies)
Discussion started by: jcdole
0 Replies

10. Solaris

Virtual Terminal (Console) showing non-global zone?

Hope that everyone is doing well today. Happy Friday. I am running an illumos (opensolaris) based system which is like SmartOS, OmniOS, and OpenIndiana I have been searching all over the Internet into various documents and forms that have to do with Solaris, Opensolaris, Illumos, and SmartOS... (3 Replies)
Discussion started by: LonnieTC
3 Replies
ttytype(1)						      General Commands Manual							ttytype(1)

NAME
ttytype - terminal identification program SYNOPSIS
type] DESCRIPTION
automatically identifies the current terminal type by sending an identification request sequence to the terminal. This method works for local, modem, and remote terminal connections, as well as for the and terminal emulators. Once the terminal has been identified, prints the terminal's type to the standard output (see terminfo(4)). This string is usually used as the value for the environment variable. If is unable to determine the correct terminal type, it prompts the user for the correct terminal identification string. Options recognizes the following options: Causes to return an ID of "unknown" instead of prompting for the terminal type if auto-identification fails. If this option is not present, interactively prompts the user for the terminal type if it is unable to determine the correct type automati- cally. Causes to prompt for the terminal type before it sends the terminal identification request sequence. If the user responds with only a carriage return, proceeds with the automatic terminal identification process. Any other response is taken as the correct terminal type. Note that the and variables are not set if the user manually enters a terminal type. The option is normally used only for terminals that do not behave well when presented with terminal identification request sequence. It gives the user a chance to respond with the correct terminal type before any escape sequences are sent that could have an adverse effect on the terminal. The option can be used in conjunction with the option. The option only inhibits interactive prompting after has failed to identify the terminal by other means. Tells to print a series of shell commands to set the and environment variables to appropriate values. In addition, the variable is set to the two-character sequence representing the appropriate erase character for the terminal (DEL for ANSI termi- nals, backspace for all others). This two-character sequence can then be used as an argument to or (see stty(1) and tset(1)). The environment variable is consulted to see which shell syntax to use for setting the environment variables. This output is normally used with a command of the form: normally attempts identification of Wyse, ANSI and HP terminals. The type argument can be used to restrict the inquiry to that required for terminals of the specified type. The accepted types are and Multiple options can be specified. Enable verbose messages to standard error. Notes Use of the option is highly recommended because many terminals support variable-size displays. This option provides the only means for automatically configuring the user environment in such a manner that applications can handle these terminals correctly. Note that and are not set if the option is used and the user manually enters a terminal type. The following steps are performed in the order indicated when identifying a terminal: 1. tries the Wyse 30/50/60 id request sequence. 2. tries the standard ANSI ID request sequence. If a response is received, it is converted to a string according to an internal table. 3. tries the HP id request sequence. 4. If none of the above steps succeed, prompts interactively for the correct terminal type unless the option has been given. may skip one or more of the first three steps, depending on the presence of options. The HP ID request sequence can switch some ANSI terminals into an unexpected operating mode. Recovery from such a condition sometimes requires cycling power on the terminal. To avoid this problem, always sends the HP identification sequence last. EXAMPLES
is most commonly used as part of the login sequence. The following shell script fragment can be used during login shell initialization: # # If TERM is not set, see if our port is listed in /etc/ttytype. # If /etc/ttytype doesn't have information for our port, run # ttytype(1) to try to determine the type of terminal we have. # # To have ttytype(1) prompt for the terminal type before trying # to automatically identify the terminal, add the "-p" option # to the "ttytype -s" command below. # if [ -z "$TERM" -o "$TERM" = network ]; then unset TERM eval `tset -s -Q` if [ -z "$TERM" -o "$TERM" = unknown ]; then eval `ttytype -s` tset -Q -e ${ERASE:-^h} $TERM fi fi WARNINGS
The terminal identification sequences sent by can cause unexpected behavior on terminals other than the Wyse 30/50/60, standard ANSI or HP terminals. If you have such terminals in your configuration, use the or options to prevent from sending sequences that cause unexpected behavior. AUTHOR
was developed by HP. SEE ALSO
csh(1), ksh(1), sh(1), stty(1), ttytype(4), environ(5). ttytype(1)
All times are GMT -4. The time now is 02:46 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy