From d77e008edd0814bceb969bcc3c47866fe87fdd85 Mon Sep 17 00:00:00 2001
From: saeedjohar <saeed_johar@yahoo.com>
Date: Mon, 4 Nov 2024 19:56:56 +0300
Subject: [PATCH] remove duplicate section

---
 README.adoc | 27 ---------------------------
 1 file changed, 27 deletions(-)

diff --git a/README.adoc b/README.adoc
index 01dc3f3..25fb1d8 100644
--- a/README.adoc
+++ b/README.adoc
@@ -36,33 +36,6 @@ Whilst udebs are not designed to be removed/upgraded/replaced, their
 install paths *should* not conflict with those of regular .deb files as
 multiarch is not supported.
 
-The existing d-i has an hd-media option; this should be investigated as a
-starting point.
-== cryptroot image
-Kernel modules must be copied into the image:
-[source]
-----
-BUILD_DIR=$(realpath build)/
-pushd <rootfs>
-sudo find usr/lib/modules \( -name 'dm-mod.*' -o -name 'dm-crypt.*' -o -name 'af_alg.*' -o -name 'algif_skcipher.*' -o -name 'libaes.*' -o -name 'aes_generic.*' -o -name 'aes-arm64.*' \) -exec cp -r --parents "{}" ${BUILD_DIR} \;
-popd
-----
-== Future Directions
-=== Automatic udeb generation
-Investigate Debian tooling to automatically turn packages into udebs.  udebs
-are heavily cut-down (even omitting uninstall scripts) and may be ideal for
-systems that are upgraded at the block device level.
-
-=== Upgrade d-i media in-place
-The d-i environment has a udeb version of dpkg, udpkg (which is only 31 kB
-installed).  Investigate possibility of an in-place upgrade from a udeb-based
-system to something debootstrap would generate.  This could be a 'stage 0.5' of
-pi-gen.
-
-Whilst udebs are not designed to be removed/upgraded/replaced, their
-install paths *should* not conflict with those of regular .deb files as
-multiarch is not supported.
-
 The existing d-i has an hd-media option; this should be investigated as a
 starting point.
 == cryptroot image