1.1 Introduction to Linux and Open Source

Content

Overview and Objectives

This section covers Linux’s place in modern technology: where it came from, how open source works, how the major distribution families compare, and why Linux ended up running most of the world’s servers and cloud infrastructure.

Learning Objectives

By the end of this section, you will be able to:

  • Explain the history of Linux from its origins to enterprise adoption
  • Explain the key principles of open source philosophy and community-driven development
  • Compare Linux with Windows and macOS in enterprise environments
  • Identify the major Linux distribution families and their use cases
  • Describe Linux’s role in modern infrastructure and cloud computing

The birth of Linux

In 1991, a 21-year-old Finnish computer science student named Linus Torvalds was frustrated with the limitations of existing operating systems available for his Intel 386 PC. He wanted something similar to the powerful Unix systems he used at university, but Unix was expensive and not designed for personal computers. So he decided to create his own operating system kernel as a hobby project.

Torvalds announced his project on a Usenet newsgroup with a now-famous message:

From: torvalds@klaava.Helsinki.FI (Linus Benedict Torvalds)
Newsgroups: comp.os.minix
Subject: What would you like to see most in minix?
Summary: Small poll for my new operating system
Date: 25 Aug 91 20:57:08 GMT
Organization: University of Helsinki

Hello everybody out there using minix -

I'm doing a (free) operating system (just a hobby, won't be big and
professional like gnu) for 386(486) AT clones. This has been brewing
since april, and is starting to get ready. I'd like any feedback on
things people like/dislike in minix, as my OS resembles it somewhat
(same physical layout of the file-system (due to practical reasons)
among other things).

I've currently ported bash(1.08) and gcc(1.40), and things seem to work.
This implies that I'll get something practical within a few months, and
I'd like to know what features most people would want. Any suggestions
are welcome, but I won't promise I'll implement them :-)

Linus (torvalds@kruuna.helsinki.fi)

PS. Yes - it's free of any minix code, and it has a multi-threaded fs.
It is NOT protable (uses 386 task switching etc), and it probably never
will support anything other than AT-harddisks, as that's all I have :-(.

He had no idea.

The key innovation wasn’t just technical — it was social. Torvalds released his kernel under the GNU General Public License, which made the source code freely available for anyone to study, modify, and distribute. That decision attracted developers from around the world who contributed improvements, bug fixes, and new features. The collaborative model that emerged became a template for successful open source projects.

By the mid-1990s, Linux had grown from a student experiment into a robust operating system. Companies began taking notice as Linux demonstrated stability, security, and performance that often exceeded commercial alternatives. The late 1990s brought the first major enterprise adoptions, with companies like IBM making billion-dollar investments in Linux development and support.

Today, Linux runs smartphones, smart TVs, the world’s fastest supercomputers, most web servers, and most cloud infrastructure. It’s genuinely hard to use the internet without touching a Linux system.

Open source

Open source is a fundamentally different approach to software development than the traditional proprietary model. The source code — the human-readable instructions that make up a program — is freely available for anyone to examine, modify, and share.

One of the most important activities of the organization called Open Source Initiative is as a standards body, maintaining the Open Source Definition. But this technical definition only scratches the surface of what makes open source powerful.

The philosophy behind open source has several key principles. First is transparency — when source code is open, anyone can inspect it for security vulnerabilities, bugs, or inefficient implementations.

This “many eyes make all bugs shallow” approach often leads to more secure and reliable software than closed-source alternatives where only a small team of developers can review the code.

Being able to read other people’s source code is an invaluable opportunity to grow as a programmer and software engineer. Nowadays, many people just browse code repositories to spot interesting code and algorithms.

Being able — and legally allowed — to take existing code and modify it to your own needs is another unique feature of open source software. In recent years, this also enabled the open source community to fork the repositories of widely used softwares like Redis and Terraform when their owning businesses decided to discontinue publishing updates under an open source license.

Second is collaboration over competition. Instead of multiple companies duplicating effort building similar solutions in isolation, open source lets developers share foundations. Some of the most widely-used software in history was built this way: the Linux kernel, the Apache web server, MySQL. Rather than starting from scratch, developers build on existing projects and focus their energy on whatever’s actually new. This has compressed software development timelines considerably.

From a business perspective, open source avoids vendor lock-in, reduces software licensing costs, and allows customization. Many successful businesses are built around open source: some by providing professional support, others by layering proprietary features on top of open source foundations.

Open source isn’t just about individual projects — it’s about communities. Successful projects develop ecosystems of users, contributors, and businesses that sustain long-term development and support. Even traditionally proprietary companies like Microsoft, Oracle, and IBM have embraced it as a core part of their technology strategy.

The downsides of open source are real, though. Many open source developers deliver tremendous work unpaid, in their spare time. Burnout is common — maintainers struggle to keep up with both the software and the user community. Large companies often benefit from open source while making demands that maintainers can’t meet. Sustainable open source is still an unsolved problem.

Linux vs. Windows vs. macOS in the enterprise

The choice of operating system isn’t just about personal preference — it’s a business decision with real implications for cost, security, performance, and flexibility.

Linux has over 80% of the server market, and that’s not accidental. Linux servers can run for months or even years without rebooting, which matters for critical applications that need to stay up. That stability comes from its Unix heritage, designed from the start for multi-user, multi-tasking server environments.

Cost is a real factor too. Windows Server requires per-core or per-user licensing that adds up fast at scale. Most Linux distributions are free to download. Organizations still pay for support, training, and tooling, but the base licensing cost is dramatically lower.

Security is another area where Linux has a structural advantage. The open source model means vulnerabilities get spotted and patched faster. Linux’s permission model is more resistant to malware than Windows by design, and removing unnecessary components reduces the attack surface significantly.

Windows holds its ground in environments built around Microsoft’s ecosystem: Active Directory, Exchange, SharePoint. Many organizations run both — Windows for desktops and office productivity, Linux for backend services and infrastructure.

macOS has a Unix foundation similar to Linux, which is why the transition feels relatively smooth for developers. But it has minimal server presence in enterprises.

The cloud picture is decisive. AWS, Azure, and Google Cloud all run primarily on Linux. Azure runs more Linux instances than Windows ones. Even the company that makes Windows ships Linux on most of its cloud infrastructure.

This means Linux skills matter regardless of what your organization uses on the desktop. Cloud, containers, and DevOps are all Linux-first. If you want to work in those areas, you’ll need to know Linux.

Linux distribution families

Linux comes in hundreds of “flavors” called distributions, or “distros” — which is often the first thing that confuses newcomers. Unlike Windows or macOS, where there’s essentially one version per company, the Linux world has many. They mostly cluster into a few families, though.

The Red Hat family is the enterprise-focused branch. Red Hat Enterprise Linux (RHEL) is the commercial flagship: long-term support, rigorous testing, and professional support services. Fedora is the community-driven testing ground for technologies that eventually make it into RHEL, which is why we use it in this course. CentOS Stream sits between the two — free, community-supported, and closely tracking RHEL development.

The Debian family emphasizes stability and open source principles. Debian itself has a reputation for being extremely stable but slow to adopt new things. Ubuntu, which is based on Debian, became one of the most popular distributions by hitting a better balance between stability and current software, plus better hardware support. Canonical’s corporate backing gives it professional support options that make it attractive for enterprise use.

The SUSE family focuses on enterprise reliability and integration with existing IT infrastructure. SUSE Linux Enterprise Server (SLES) competes with RHEL in the enterprise market, and openSUSE is the community version. SUSE is particularly strong in Europe and has solid SAP integration.

Arch Linux is a rolling-release distribution — it continuously delivers updates rather than releasing discrete versions. Minimalism is a design goal, but its Arch User Repository (AUR) compensates with an enormous software catalog. Arch is also known for the ArchWiki, which is among the best Linux documentation anywhere.

Each family uses a different package management system. Red Hat uses RPM packages managed by DNF (or the older YUM); Debian uses DEB packages with APT; SUSE uses RPM with Zypper; Arch uses binary PKG packages with Pacman. This matters in practice — it affects automation scripts, deployment procedures, and how you troubleshoot.

In enterprise environments, the choice between distributions usually comes down to support contracts, compliance requirements, existing systems, and what the team already knows. Many organizations standardize on one family to keep training and automation simple. For a career perspective: RHEL and Ubuntu Server are the most common targets for enterprise work; Ubuntu and Fedora are popular for cloud-native development; and working across multiple families is common in DevOps.

Linux in modern infrastructure and cloud computing

Cloud computing cemented Linux’s infrastructure role. AWS built its entire platform on Linux. Azure, despite coming from Microsoft, now runs more Linux instances than Windows ones. Google Cloud standardized on Linux because Google has run Linux internally for decades. Regardless of which cloud platform you work with, you’ll be interacting with Linux.

Containers deepened that dependence. Docker runs natively on Linux. Kubernetes was designed for Linux. Windows containers exist, but the vast majority of containerized workloads run on Linux. The DevOps toolchain — Ansible, Terraform, Jenkins, GitLab CI/CD — was built Linux-first. Microservices architectures rely on Linux containers and Linux-based orchestration.

Linux has also spread into edge computing and IoT: smart city infrastructure, industrial automation, automotive systems. It runs well on limited hardware without a graphical interface, which matters a lot when you’re running on a device with 512MB of RAM.

Linux skills matter across nearly every modern IT role. System administration, cloud architecture, DevOps, software development — all of them involve Linux. If you’re building a career in any of those areas, this isn’t optional background knowledge.

Real-world context

In practice, you’ll encounter Linux in multiple contexts at any organization — web servers, cloud infrastructure, CI/CD pipelines, containers. Understanding its history explains why certain design decisions were made and why Linux ends up on so much critical infrastructure.

Open source philosophy isn’t just academic. It shapes how you evaluate and select technologies, how you contribute back, and how you build your professional network. A lot of IT careers grew out of open source contributions.

Distribution knowledge becomes practical when you’re choosing a platform for a new project, migrating between environments, or debugging issues that turn out to be distro-specific. Many specialists focus on one family, and that specialization shapes career opportunities.

Common Pitfalls

A common misconception is that “Linux is Linux” — that distributions are basically interchangeable. They’re not. Commands, file locations, and package names can differ enough between families to cause real confusion. Learn the characteristics of the specific distributions you’ll be working with.

Relatedly, don’t assume open source means unsupported or unprofessional. Enterprise open source solutions often have more rigorous development processes and better support options than proprietary alternatives.

If your career goals involve server administration or cloud computing, don’t focus exclusively on desktop Linux. Desktop experience is valuable for learning, but server-focused distributions and their enterprise use cases are what you’ll actually need.

Finally, avoid getting too attached to a single distribution. The Linux ecosystem is diverse, and professionals need to be comfortable moving between distros as business needs change. Distro hopping is a hobby for some people, but adaptability is a professional skill.

  1. “The Linux Command Line” by William Shotts — An introduction to Linux fundamentals with practical examples and clear explanations of core concepts.

  2. “How Linux Works” by Brian Ward — A deeper dive into Linux internals and the reasoning behind Linux’s design decisions.

  3. “The Cathedral and the Bazaar” by Eric S. Raymond — A classic essay on open source development and the philosophy behind it.

  4. Red Hat Enterprise Linux documentation — Official documentation for enterprise Linux deployment and management.

Assessment

Multiple Choice Questions

Question 1: Who created the Linux kernel and in what year?

  • a) Linus Torvalds in 1991
  • b) Richard Stallman in 1985
  • c) Andrew Tanenbaum in 1987
  • d) Ken Thompson in 1969

Question 2: Which of the following best describes the open source philosophy?

  • a) Software should be free of cost but not modifiable
  • b) Only educational institutions should have access to source code
  • c) Source code should be available for inspection, modification, and redistribution
  • d) Software companies should share code only with their customers

Question 3: What is the primary package management tool used in Fedora Linux?

  • a) APT
  • b) Zypper
  • c) Portage
  • d) DNF

Question 4: Which distribution family does Ubuntu belong to?

  • a) Red Hat family
  • b) Debian family
  • c) SUSE family
  • d) Arch family

Question 5: What percentage of web servers run on Linux?

  • a) Approximately 30%
  • b) Approximately 50%
  • c) Approximately 80%
  • d) Approximately 65%

Question 6: Which license did Linus Torvalds choose for the Linux kernel?

  • a) MIT License
  • b) GNU General Public License (GPL)
  • c) BSD License
  • d) Apache License

Question 7: What is the primary advantage of Linux in cloud computing environments?

  • a) Better graphics performance
  • b) Built-in antivirus protection
  • c) Lower licensing costs and better scalability
  • d) Automatic backup capabilities

Question 8: Which of the following is NOT a major Linux distribution family?

  • a) Puppy family
  • b) Debian family
  • c) Red Hat family
  • d) SUSE family

Short Answer Questions

Question 9: Explain why Linux has become dominant in server and cloud computing environments, mentioning at least three specific advantages.

Question 10: Describe the key differences between the Red Hat and Debian distribution families, including their package management systems and typical use cases.

Question 11: How has the open source development model contributed to Linux’s success, and what are the implications for organizations considering Linux adoption?

Updated 2026-03-10