Video summary

La revolucion de SO (Revolution OS).2001 (Documental en V.O.Sub. español

Main summary

Key takeaways

Science and Nature

Scientific concepts, discoveries, and nature phenomena presented

Computer science / software engineering

The role of an operating system (OS)

  • An OS provides resources and infrastructure so that applications/programs can run.
  • The OS “does nothing” by itself until programs request resources such as:
    • files
    • connectivity (networking)
    • other system services

Open-source and free-software collaboration models

  • Software can be shared and improved via community contributions, rather than restricted by:
    • proprietary licensing
    • IP control
  • “Free software” is defined as freedom, not price:
    • “free speech, not free beer”

Legal/organizational mechanism: Copyleft

  • Copyleft flips copyright so that redistributed versions must keep the same freedoms.
  • The GNU General Public License (GPL) is referenced as an example of this philosophy/community intent.

Systems/software architecture

  • Kernel approaches
    • Monolithic kernel: e.g., Linux is described as monolithic (the OS treated as one indivisible entity).
    • Microkernel: contrasted idea where the kernel is a set of communicating server processes via protocols.
  • Complexity/debugging tradeoffs
    • GNU kernel design is described as partitioned into many smaller, asynchronously communicating programs.
    • This approach is powerful, but hard to debug, reportedly taking years to stabilize.

Toolchain components needed for a Unix-like system

Examples listed include:

  • kernel
  • compiler
  • debugger
  • text editor
  • text formatters
  • mailers (and other related toolchain utilities)

Real-world software adoption driver

  • The Apache web server is framed as the “killer app” that helped Linux adoption.
  • Adoption is described as aligning with broader growth in:
    • the internet
    • ISPs
  • Apache’s impact is attributed to:
    • reliability
    • flexibility/extensibility
    • cost effectiveness versus Windows/NT for server farms

Distributed development vs. traditional engineering

  • “Cathedral vs. Bazaar”
    • Cathedral:
      • hierarchical
      • tightly specified
      • long release intervals
    • Bazaar:
      • peer-to-peer decentralized
      • short release intervals
      • continual external feedback
      • intense peer review

No nature phenomena

  • The content is entirely technological and socio-legal rather than scientific-natural events.

Methodology / framework outlined

Development and growth: “free software → GNU/Linux”

A conceptual process:

  1. Start with GNU/free software projects (tools/toolkit).
  2. Build and refine core components (e.g., compiler/toolchain, editor/debugger, etc.).
  3. Integrate with a kernel to form a complete system:
    • GNU toolkit + Linux kernel → GNU/Linux
  4. Use licenses (GPL/copy-left) to preserve freedoms and ensure community continuation.
  5. Scale adoption through:
    • distributed contribution
    • business support
    • high-demand applications (e.g., Apache)

“Cathedral vs. Bazaar” software development styles

Cathedral

  • Tight objectives/specs
  • Small hierarchical groups
  • Long release intervals

Bazaar

  • Decentralized peer-to-peer style
  • Very short release intervals
  • Constant feedback solicitation
  • Massive independent peer review

Featured researchers / sources (named in the subtitles)

  • Craig Mundy (Microsoft executive referenced in an anecdote)
  • Richard Stallman (founder of the Free Software Foundation; GNU/free software)
  • Bill Gates (referred to via a “open letter to hobbyists” citation)
  • Linus Torvalds (Linux kernel)
  • Mark Ewing (Red Hat origin)
  • Bob Young (Red Hat co-founder)
  • Eric Raymond (The Cathedral and the Bazaar; influenced modern framing)
  • Tim O’Reilly (O’Reilly Associates; conference/paper circulation)
  • Christine Peterson (Foresight Institute; involved in “open source” naming/meetings)
  • John “Mad Dog” Hall (referenced as participating by phone)
  • Todd Anderson (referenced as participating)
  • Sam Oman (runs Penguin Computing; referenced as participating)
  • Bruce Perens (Debian Free Software Guidelines origin; referenced in “open source definition” derivation)
  • Linus Torvalds (also framed again around Linux World appearance and “GNU/Linux” naming)
  • Jim Barksdale (Netscape decision-maker referenced)
  • Mark Andre (Netscape co-founder referenced)
  • Larry Augustine (Linux World conference chair/CEO of VA Linux Systems referenced)
  • Steve Ballmer (quoted about “open source” meaning more than releasing source code)
  • Matt (associated with a Windows refund idea in a cited “Slashdot” reference)
  • Lenus Torvald’s pronunciation discussion (spelling/pronunciation variation: “Linus (Swedish/Finnish), Lionus (English)”; same person)

Organizations / sources mentioned (not individual researchers, but cited as sources/projects)

  • MIT AI Lab
  • GNU Project / Free Software Foundation (FSF)
  • Berkeley Unix (BSD) and AT&T
  • Homebrew Computer Club
  • Debian (policy/guidelines)
  • Linux distributions (e.g., Red Hat, Debian, etc.)
  • Netscape and Mozilla-era browser context
  • Microsoft (as a proprietary-software model competitor)
  • O’Reilly Associates
  • VA Linux Systems
  • Signis Software
  • Penguin Computing
  • Apache web server
  • FreeBSD (mentioned as an OS ecosystem context for Apache/Linux communities)

Original video