update notes

docs/notes.md

@@ -11,4 +11,15 @@
   - injected at install time: https://containers.github.io/bootc/building/kernel-arguments.html#kernel-arguments-injected-at-installation-time
 - users and groups: https://containers.github.io/bootc/building/users-and-groups.html
 - API: https://containers.github.io/bootc/bootc-via-api.html
-- 
+
+
+## thoughts on streamlining
+
+- current methods of generating iso and disk images suitable for running a vm or host is a bit painful
+- pxe methods seem to mostly target coreos, which doesn't align well with the ublue (or bootc) images at this time, as far as I can tell.
+- it seems like there should be a way convert the container to a running disk image without jumping through so many hoops (with multiple install/build cycles).
+- pxe/disk/iso based bootstrap -> merge install time config (anaconda/kickstart/...) from kernel command line/network/etc -> deploy ostree-based image -> reboot/kexec
+  - seems like a pxe-boot image containing anaconda *could* do this
+  - current iso-based systems basically seem to deploy an entire separate os for bootstrapping
+  - even configuring auto-rebase through kickstart takes too long, multiple deploy, write, reboot stages
+  - leverage something like capt-based deployment???