How the kernel uses an initramfs

diff --git a/index.html b/index.html
index 2c572e96531980a5e75c9cac5b45569c423d650d..b13a32d6979ba6aa9f52256fb323467def87a01c 100644 (file)
--- a/index.html
+++ b/index.html
@@ -72,8 +72,8 @@
       it can't read them from the root filesystem
     </li>
     <li>
       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>
     </li>
   </ul>
 </div>


@@ -82,6 +82,30 @@
   <img src="yo-dawg.jpeg" width="90%" />
 </div>
 
   <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>
 <div class="slide">
   <h1>Questions?</h1>
 </div>