EMB-220 · Embedded Linux & BSP · Practitioner

Init Systems & Fast Boot — full syllabus

systemd and the alternatives, plus measuring and cutting boot time to a target.

Duration2 full days in person · 4 half-days online
Cohortmax 14 in person · 20 online
Pricefrom SAR 5,250 in person · local pricing per city
Delivery35% principles · 20% guided investigation · 45% engineering studio

Who this course is for

Embedded engineers who must pick an init system and hit a boot-time number — product teams with a hard requirement like 'UI in under five seconds' and a distaste for unmeasured claims.

Prerequisites

Course outline

Day 1 — Init systems in production

  • What PID 1 must do and what it is not for
  • systemd: units, targets, dependencies and socket activation
  • Debugging systemd boot: systemctl, journald and the critical chain
  • BusyBox init and minimal alternatives: what you gain and what you maintain yourself
  • Choosing per product: footprint, features, updates and team skill

Day 2 — Measuring and cutting boot time

  • A measurement discipline: define the moment 'booted' means, then measure it
  • systemd-analyze, bootchart and serial timestamping with grabserial
  • Kernel-side cuts: initcall_debug, deferred probing, modules vs built-in
  • Userspace-side cuts: ordering, socket activation, precomputation
  • Meeting a hard target without breaking updates or maintainability

Hands-on labs

  1. Lab: Convert a shell-script service to a systemd unit with correct dependencies, then break a dependency and read the failure
  2. Lab: Socket-activate a service and measure the ordering change it produces in the critical chain
  3. Lab: Capture a boot timeline three ways — systemd-analyze, bootchart and grabserial on the lab board — and reconcile them
  4. Lab: Cut a measured chunk of boot time using kernel and userspace techniques, keeping a before/after evidence log
  5. Lab: Build the same rootfs with BusyBox init, and document what you had to re-implement by hand

Capstone project

Take a provided image with a stated boot-time target to a working result: define the 'booted' event, measure with two independent methods, apply kernel and userspace reductions in order of evidence, and deliver the tuned image with a before/after timeline and a written account of every change that mattered — and every change that did not.

What you leave with

Upcoming dates

DatesWhereSeatsEarly birdRegular
1 Nov – 2 Nov 20262 full days RiyadhIn person · KAFD Conference Centre 4 of 14 —SAR 5,250
8 Nov – 9 Nov 20262 full days Kuwait CityIn person · Al Hamra Tower 9 of 14 KWD 390until 9 OctKWD 430
8 Nov – 9 Nov 20262 full days MuscatIn person · Knowledge Oasis Muscat 4 of 14 OMR 490until 9 OctOMR 540
15 Nov – 18 Nov 20264 half-days Gulf bandLive online · 09:00–13:00 GMT+3 16 of 20 US$900until 16 OctUS$1,000
16 Nov – 17 Nov 20262 full days OttawaIn person · Kanata North Tech Park 9 of 14 CAD 1,710until 17 OctCAD 1,900
23 Nov – 24 Nov 20262 full days TorontoIn person · MaRS Discovery District 4 of 14 CAD 1,710until 24 OctCAD 1,900
23 Nov – 24 Nov 20262 full days LondonIn person · Shoreditch Works 9 of 14 GBP 980until 24 OctGBP 1,090
23 Nov – 26 Nov 20264 half-days Europe bandLive online · 09:00–13:00 CET 5 of 20 US$900until 24 OctUS$1,000
23 Nov – 26 Nov 20264 half-days Americas bandLive online · 13:00–17:00 ET 10 of 20 US$900until 24 OctUS$1,000
30 Nov – 1 Dec 20262 full days BerlinIn person · Factory Görlitzer Park 4 of 14 EUR 1,160until 31 OctEUR 1,290

Book a seat, or bring this course to your team

Seats can be reserved online; private delivery runs on-site or live online, adapted to your stack.

Course page & booking

Questions about fit or prerequisites? Email hello@kernelsystems.academy. To save this syllabus, print this page to PDF from your browser.