From 7da7f251892eb24de2d10fa9b76821903984abad Mon Sep 17 00:00:00 2001
From: Ben Hutchings <ben@decadent.org.uk>
Date: Sat, 8 Nov 2014 16:56:37 +0000
Subject: [PATCH] How the kernel uses an initramfs

---
 index.html | 28 ++++++++++++++++++++++++++--
 1 file changed, 26 insertions(+), 2 deletions(-)

diff --git a/index.html b/index.html
index 2c572e9..b13a32d 100644
--- a/index.html
+++ b/index.html
@@ -72,8 +72,8 @@
       it can't read them from the root filesystem
     </li>
     <li>
-      Solution: boot loader provides a bundle of files to the
-      kernel
+      Solution: boot loader provides a bundle of files
+      (initramfs image) to the kernel
     </li>
   </ul>
 </div>
@@ -82,6 +82,30 @@
   <img src="yo-dawg.jpeg" width="90%" />
 </div>
 
+<div class="slide">
+  <h1>How the kernel uses an initramfs</h1>
+  <ul class="incremental">
+    <li>
+      Kernel <em>always</em> mounts an initial root filesystem using
+      either ramfs or tmpfs
+    </li>
+    <li>
+      If the boot loader provides an initramfs image, kernel
+      unpacks it into this filesystem, then runs <tt>/init</tt>
+    </li>
+    <li>
+      The initramfs init system is then responsible for mounting
+      the real root filesystem and running the real <tt>init</tt>
+      <ul class="incremental">
+	<li>
+	  Although it is not <em>required</em> to hand over at all
+	  - e.g. debian-installer
+	</li>
+      </ul>
+    </li>
+  </ul>
+</div>
+
 <div class="slide">
   <h1>Questions?</h1>
 </div>
-- 
2.39.5