Definition:
Linux is an open-source kernel started by Linus Torvalds in 1991 that manages communication between hardware and the programs in a computer system. It handles functions such as processes, memory, devices, file systems, networking, and permissions.
In common usage, Linux also refers to operating systems built around that kernel. Many combine Linux with tools from the GNU project and other components, so they are also called GNU/Linux. A distribution assembles these elements, configures them, and establishes a method for installation, updates, and support.
Table of contents
System origins
The GNU project began in 1983 with the aim of creating a free Unix-compatible operating system. It had developed compilers, libraries, a shell, and many utilities, but it did not have a complete general-purpose kernel when Linus Torvalds released the first Linux kernel in 1991.
Combining the kernel with GNU tools made it possible to build functional systems. Linux and GNU/Linux can therefore refer to different things depending on context: Linux precisely identifies the kernel, while GNU/Linux highlights one of the combinations that form a complete operating system.
The Linux kernel project distributes its source code under the GPL-2.0 licence. The software remains protected by copyright, and its licence defines how it may be used, modified, and redistributed. Open source does not mean an absence of ownership, maintenance, or legal conditions.
Linux architecture
The kernel works between the hardware and user space, where applications and services run. A Linux-based system normally integrates several coordinated layers:
- Kernel: Manages processors, memory, devices, networking, processes, and security mechanisms.
- User space: Includes libraries, commands, services, and tools that use kernel interfaces.
- Init system: Starts and supervises the services needed for the computer or server to operate.
- Package manager: Installs, updates, and removes programs from repositories defined by the distribution.
- Interface: May be a terminal, graphical desktop, remote panel, or a combination of environments.
The kernel alone does not constitute the complete user experience. Behaviour, available applications, update policy, and administration tools depend on the chosen distribution and configuration.
Distribution ecosystem
A distribution integrates the kernel with the rest of the required software and maintains package repositories. Differences between distributions affect the support cycle, frequency of change, package formats, and administration, as well as their intended users.
Debian and Ubuntu share the DEB package family; Fedora and Red Hat Enterprise Linux use the RPM ecosystem; Arch Linux follows a rolling-release model; and openSUSE provides alternatives with different release cadences. These families are not editions of a single product: each project maintains its own decisions, repositories, and support conditions.
The choice depends on the workload, hardware, team experience, stability requirements, and maintenance period. For a production server, predictable updates and available support normally matter more than immediately adopting the newest version of every component.
Digital infrastructure
Linux is used in many environments that support websites, applications, and digital services. Common uses include:
- Hosting and web services: Running HTTP servers, databases, cache systems, content management systems, and applications.
- Cloud and containers: Creating virtual machines, container images, and orchestration platforms.
- Development and automation: Programming environments, continuous integration, deployments, and scheduled tasks.
- Data and measurement: Processing logs, data pipelines, storage, and observability tools.
- Devices and networks: Routers, embedded systems, televisions, industrial equipment, and other connected devices.
Android uses the Linux kernel but adds its own application platform, libraries, interface, and distribution model. This does not make Android a conventional GNU/Linux distribution, even though both share an essential part of their technical foundation.
Operation of digital assets
The server operating system affects how a website is deployed, resources are allocated, certificates are managed, tasks are scheduled, and logs are collected. Poor configuration can affect availability, response time, and data integrity, even when the content or application has not changed.
Compatibility also matters. Tools, browsers, and applications may provide different packages for each distribution or architecture. Testing should reproduce the real execution environment and account for dependencies, versions, and permissions instead of assuming that every Linux-compatible program will behave identically on any system.
In analytics and digital marketing, Linux often works behind servers, server-side tags, import processes, dashboards, and automations. Access to logs and data should be limited according to each person’s role. The technical ability to collect information does not replace an appropriate legal basis, data minimisation, or applicable retention periods.
System governance
Open development allows code to be reviewed and fixes to be distributed, but it does not protect an installation automatically. Security depends on maintenance and specific decisions:
- Updates: Apply patches to the kernel, libraries, services, and applications through a controlled process.
- Privileges: Give users and processes only the permissions they need.
- Exposure: Keep only necessary ports and services active, with suitable network rules.
- Monitoring: Review logs, alerts, capacity, errors, and configuration changes.
- Recovery: Maintain tested backups, restoration procedures, and a distribution with current support.
Linux provides control, automation, and a broad ecosystem, but its outcome depends on the distribution, support, compatibility, and administration capability. Choosing it does not remove operating costs or guarantee performance, privacy, or security by itself.