Skip to main content
In this lesson, you’ll learn various methods to log in to a Linux system—both locally and remotely—using graphical and text-mode consoles. We will cover not only how to perform these logins but also the reasons behind using each method.

Login Methods Overview

There are four common methods for logging in:
  1. Logging into a local Linux system using a text-mode console.
  2. Logging into a local Linux system using a graphical-mode console.
  3. Logging into a remote Linux system using text-mode login.
  4. Logging into a remote Linux system using graphical-mode login.
The image illustrates four login methods: local text-mode console, remote text-mode login, local graphical-mode console, and remote graphical-mode login. Each method is represented with icons showing a user and a console or graphical interface.
You’ll often come across terms such as console, virtual terminal, and terminal emulator. A console is a display for system messages and commands, whereas a terminal emulator is a graphical application that mimics this behavior within a window.
• Console: Provides text display and command input.
• Terminal Emulator: A graphical application that replicates the console’s functionality.

Text-Mode Login Examples

Below is an example of a text-mode login screen on a CentOS system:
Historically, these terms originated when computers were expensive and shared among many users through physical consoles or terminals. Today, even though hardware has evolved, these concepts continue to exist in software form. For example, during the boot process, the system console displays diagnostic messages. Consider this snippet from a boot log:
After the system has booted, you can switch to another virtual terminal. For example, pressing Ctrl-Alt-F2 takes you to VT2:

Graphical User Interface (GUI) Logins

For systems equipped with a GUI, you typically open a terminal emulator to enter your commands. When logging in to a local GUI, you might see a list of user accounts. For example:
The image shows a CentOS login screen with a list of user accounts, highlighting one named "Aaron." The screen is labeled "Local GUI" and includes the KodeKloud logo.
Always remember to log out once your work is complete. For server-oriented Linux systems (those that typically operate without a GUI), you will see a login prompt asking you to enter your username and password manually:
Note: The password is not echoed on the screen as you type. Once you are ready to exit, use the command exit to log out:

Remote GUI Access

Connecting to a remote server with a graphical interface can vary based on server configurations. Administrators might enable:
  • Virtual Network Computing (VNC), which requires you to install a VNC client.
  • Remote Desktop Protocol (RDP), often used by Windows users with the built-in Remote Desktop Connection utility.
In both cases, you generally open the application, enter the remote system’s IP address, provide your login credentials, and connect.
The image shows a menu with two options for remote GUI access: VNC and RDP.

Remote Text-Mode Access via SSH

For remote text-based logins, the most widely used tool is the OpenSSH daemon. Unlike Telnet, SSH (Secure Shell) encrypts the communication, ensuring that sensitive data like passwords remains protected during transmission.
SSH is highly secure and has been proven over many years. Always use SSH for remote text-mode logins to maintain proper security standards.
A comparison image below shows that SSH (secured with a green lock) is far more secure than Telnet (which displays a red lock):
The image compares remote text-mode login methods, showing SSH as secure with a green lock and Telnet as insecure with a red lock.
If you are following along on a virtual machine, log in locally and run the following command to check your machine’s IP address. The output highlights an example IP address (192.168.0.17) which you can use to simulate a remote server login:
This IP address identifies the server running the SSH daemon, which listens for remote connections. To connect from your local machine, use an SSH client. Most macOS and Linux systems come with an SSH client pre-installed. Simply open your terminal and initiate the connection. For example, listing files in a local session might look like:

Connecting from Windows

Earlier Windows versions required third-party SSH clients such as PuTTY. However, modern versions like Windows 10 include a native SSH client. To connect to a remote server, open Command Prompt (type “cmd” in the Start Menu) and run:
Replace “aaron” with your actual username and “192.168.0.17” with your server’s IP address. After executing the command, you will be prompted to enter your password:
Once connected, you can perform the exercises in this lesson within your SSH session.
The demonstration above walks you through various login approaches available on Linux systems. Enjoy exploring these methods and happy learning!

Watch Video