vt

Scan a specific file for viruses

$ vt scan file [path/to/file]

$ vt scan url [url]

$ vt analysis [file_id|analysis_id]

$ vt download [file_id] --output [path/to/directory] --zip --zip-password [password]

$ vt init

$ vt domain [url]

$ vt url [url]

$ vt domain [ip_address]

The term 'vt' commonly refers to a Virtual Terminal or Virtual Console in Linux. There is no standalone 'vt' command in standard Linux distributions. Operations related to Virtual Terminals are typically handled by commands like chvt or openvt.

chvt synopsis:
chvt N

openvt synopsis:
openvt [options] [program [arguments...]]

N (for chvt)
    The virtual terminal number to switch to. Typically a number from 1 to 63.

-c N (for openvt)
    Specify the console number N to use. If not specified, openvt will try to find the first available VT.

-e (for openvt)
    Execute the specified command in a new session. This is the default if a command is given and no VT is specified.

-f (for openvt)
    Force switching to a virtual terminal even if it's already in use. Use with caution.

-l (for openvt)
    Make the new virtual terminal a login shell. This usually means running /bin/login.

-s (for openvt)
    Switch to the new virtual terminal immediately after the command is executed. This is useful when running a single command that takes over the VT.

-u (for openvt)
    Run the program as the invoking user instead of root (if invoked as root). Requires the invoking user to be logged in on the active console.

-v (for openvt)
    Be verbose. Display more information about what openvt is doing.

program [arguments...] (for openvt)
    The command or program to execute on the new virtual terminal, along with its arguments. If omitted, a default shell or login session is started.

The term 'vt' is commonly used as an abbreviation for 'Virtual Terminal' or 'Virtual Console' in Linux. Unlike commands like 'ls' or 'grep', 'vt' itself is not a standalone executable command found in standard Linux distributions. Instead, it refers to the conceptual environment that provides multiple independent login sessions on a single physical console.

Linux systems typically provide several virtual terminals (usually accessible via Ctrl+Alt+F1 through Ctrl+Alt+F6, with the graphical environment often on F7). These allow users to have multiple text-based sessions running concurrently, each with its own shell, processes, and environment. Commands like chvt and openvt are used to programmatically interact with and manage these virtual terminals, such as switching between them or launching applications on a new one.

The term 'vt' is not a direct command, which can be a source of confusion. Commands like chvt and openvt often require root privileges (or be part of a 'setuid' helper program) to operate on virtual terminals because they directly interact with the kernel's console device. Misuse of these commands, especially openvt with the -f option, can disrupt other users' sessions or system stability.

Graphical display managers (like GDM, SDDM, LightDM) typically manage a dedicated virtual terminal (often F7 or F1) for the graphical desktop, which might behave differently than the text-based VTs.

Users typically switch between virtual terminals using key combinations:
Ctrl+Alt+F1: Usually the first text console.
Ctrl+Alt+F2 to Ctrl+Alt+F6: Additional text consoles.
Ctrl+Alt+F7 (or higher): Often where the graphical desktop environment runs (e.g., GNOME, KDE).

It's important to distinguish Virtual Terminals (VTs) from Pseudo-terminals (PTYs). VTs are direct interfaces to the kernel's console driver, providing full control over the physical display and keyboard. PTYs, on the other hand, are software emulations of terminals, commonly used by terminal emulators (like GNOME Terminal, xterm), SSH sessions, and screen/tmux sessions. While both provide a command-line interface, PTYs operate at a higher level, abstracting away the direct hardware interaction that VTs provide.

Virtual Terminals (VTs) have been a fundamental component of Unix-like operating systems since their early days, allowing a single physical terminal (or later, a computer monitor and keyboard) to host multiple independent sessions. In Linux, the concept of VTs was inherited and expanded upon, providing a robust mechanism for multitasking even before the widespread adoption of graphical user interfaces.

Early Linux systems heavily relied on text-based VTs for all user interaction, with users frequently switching between them for different tasks. The commands like chvt and openvt were developed to provide programmatic control over these VTs, allowing scripts or system processes to manage console sessions. While graphical environments are now dominant, VTs remain crucial for troubleshooting, server management, and as a fallback in case of GUI issues.

chvt(1), openvt(1), deallocvt(1), console_codes(4), kbd_mode(1), setvtrgb(8)