Understanding Erlang Kernel
summary
Erlang boots about forty BEAM processes (39 shown) and walks through how a simple hello world triggers module loading, the code_server, and IO flow via a group leader message protocol rather than direct printing. Start-up is driven by a binary start.boot (with an init_debug option), interactive vs embedded modes change dynamic code loading, and the kernel uses an init process, a user process and an application master plus a helper child (the two “lonely” processes 45/46) to avoid deadlocks during supervised startup.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:43Agenda
- 1:58Live Demo
- 2:36Outline
- 2:55Processes
- 5:03PID
- 6:46New Process
- 7:39OTP Ring 0
- 8:16CPU Protection Rate
- 9:09OTP and Beijing City
- 10:12Boot files
- 11:10Script
- 11:56Interactive Mode
- 16:52Code Server
- 19:32Group Leader
- 21:04IO Protocol
- 27:28User Drive
- 30:24Application Master
related talks
48mGetting to Know the Erlang Virtual Machine, the BEAM
26mInstant-Launch Erlang Executables
42mThe Soul of Erlang and Elixir
01h 03mThinking Erlang in a connected world
42mIntroduction to Elixir for Rubyists
48mElixir by the Bellyful
31mHow does fault tolerance work in Erlang
49mAn Introduction to Erlang From behind the Trenches