LICM study materials
LICM study resources

LICM: The Linux Community and a Career in Open Source

LICM · Work through your exam, one topic at a time.

All guide sections

The Linux Community and a Career in Open Source

Domain 1 - The Linux Community and a Career in Open Source

This domain tests whether you understand where Linux came from, who builds it, and how open source licensing shapes what you may legally do with software. Expect questions on distributions, common applications, IT roles, and the difference between copyleft and permissive licences.

Core rules

  • Free software, per the FSF's four freedoms, means you may run the program for any purpose, study and change it, redistribute copies, and distribute modified versions. Source code access is the precondition.
  • Copyleft (GPLv2, GPLv3, LGPL) requires derivative works distributed to others to carry the same licence. Permissive licences (MIT, BSD, Apache 2.0) allow proprietary redistribution as long as attribution is kept.
  • The Linux kernel is licensed GPLv2; it is one component, not the whole OS - a distribution bundles kernel, GNU tools, package manager and applications.
  • Families: Debian (Debian, Ubuntu, Linux Mint) use dpkg/apt and .deb; Red Hat (RHEL, Fedora, CentOS Stream) use rpm/dnf; SUSE (SLES, openSUSE) use rpm/zypper.
  • Roles include system administrator, DevOps engineer, security analyst, developer, DBA and support engineer.

Worked example

A vendor wants to ship a product built on a GPLv3 library and keep the rest of the source closed. Reasoning: GPLv3 obligations attach to the library and to the combined work that derives from it, so they must publish the modified library source and grant recipients the same freedoms. The rest of their own code, if not derived from the library, stays proprietary - or they could choose a permissively licensed library instead.

Traps

  • Confusing "free" with zero price; the exam means freedom.
  • Believing Linux is one company's product, or that Ubuntu is a GNU project distribution alone.
  • Assuming a permissive licence forbids commercial use - it does not.
  • Mixing up which package manager belongs to which distribution family.