Loading system evidence
Loading system evidence
Build a supportable Ubuntu and ROS 2 workstation, then learn how to recover it when installation, boot, drivers, or overlays fail.
Sign in to start - freeOutcome
Build
A versioned workstation runbook with recovery evidence and a reproducible ROS workspace.
Sample incident
Choose a workable environment for simulation without buying unnecessary hardware.
Full syllabus
Match native Ubuntu, dual boot, WSL, virtual machines, and remote workspaces to hardware and learning goals.
Prepare backups, recovery keys, Fast Startup, free space, and a reversible installation plan.
Identify firmware mode, validate media, and preserve the existing EFI system partition.
Allocate root, optional data, swap, and EFI mounts with recoverable sizing decisions.
Use boot entries, TTY, recovery mode, live media, and logs to recover common workstation failures.
Use filesystems, permissions, processes, services, logs, devices, and networks as observable system layers.
Align Ubuntu, ROS distribution, repositories, locale, rosdep, and shell setup.
Control underlays, overlays, dependencies, clean builds, and machine-readable environment evidence.
Playgrounds
Small, functional experiments that reveal the math and evidence behind this course’s failures. Open them alongside the labs.
Compare matching a serial device by kernel name, idVendor/idProduct, or serial, and see which survives a replug into a new port.
udev rules / device symlink / ttyUSB
Live controlsSee how underlay/overlay sourcing order sets AMENT_PREFIX_PATH and decides whether your rebuilt package or the system copy runs.
colcon overlay / ament / source setup.bash
Live controlsCompare referencing a serial port by ttyUSB index versus a /dev/serial/by-id path across replugs and other present devices.
serial port / by-id path / ttyUSB enumeration