ideas

README.html

@@ -655,9 +655,15 @@ <h1>Notes</h1>
 <div class="section" id="issues-future-implementations">
 <h1>Issues / Future Implementations</h1>
 <ul class="simple">
+<li>get UUIDs during boot<ul>
+<li>more portable; UUIDs not hardcoded into initcpio hook</li>
+<li>no need to rebuild linux image with UUID changes</li>
+</ul>
+</li>
 <li>use <em>getopts</em> to easily allow grouping command line options together</li>
 <li><em>--rsync</em> option with <em>status=progress</em> (maybe use rsync
 automatically if installed)</li>
+<li>option to create a unique hostname for each RAM boot instance</li>
 <li>improve security features<ul>
 <li>test compatibility with full disk encryption</li>
 <li>option to require removal of boot media before starting userspace</li>
@@ -667,17 +673,6 @@ <h1>Issues / Future Implementations</h1>
 </li>
 <li><em>flush</em> action to sync the RAM filesystem back to the
 initial boot device</li>
-<li>use config file?<ul>
-<li>great for setting a bunch of options at once</li>
-<li>probably shouldn't read and parse config file during
-pre-userspace boot for security/basic functionality reasons;
-hooks should be rebuilt and linux boot image regenerated with
-every config file change</li>
-<li>implement some type of post-successful-RAM-load hooks
-or scripts to make changes after userspace is loaded
-(<em>systemd</em> hook?)</li>
-</ul>
-</li>
 <li>test on other distros</li>
 </ul>
 </div>

README.rst

@@ -143,11 +143,19 @@ often exhibit a dramatic improvement in RAM sync times.
 Issues / Future Implementations
 ===================================
 
+*   get UUIDs during boot
+
+    +   more portable; UUIDs not hardcoded into initcpio hook
+
+    +   no need to rebuild linux image with UUID changes
+
 *   use *getopts* to easily allow grouping command line options together
 
 *   *--rsync* option with *status=progress* (maybe use rsync
     automatically if installed)
 
+*   option to create a unique hostname for each RAM boot instance
+
 *   improve security features
 
     +   test compatibility with full disk encryption
@@ -160,19 +168,6 @@ Issues / Future Implementations
 *   *flush* action to sync the RAM filesystem back to the
     initial boot device
 
-*   use config file?
-
-    +   great for setting a bunch of options at once
-
-    +   probably shouldn't read and parse config file during
-        pre-userspace boot for security/basic functionality reasons;
-        hooks should be rebuilt and linux boot image regenerated with
-        every config file change
-
-    +   implement some type of post-successful-RAM-load hooks
-        or scripts to make changes after userspace is loaded
-        (*systemd* hook?)
-
 *   test on other distros