manual update

docs/README.adoc

@@ -152,7 +152,7 @@ The recommended option is to use https://bdisk.square-r00t.net/[BDisk^] (the aut
 . `echo "aif-git" > *<BDisk directory>*/extra/pre-build.d/root/packages.both`
 . If you want automatic root login on TTY1 like the Arch install ISO (optional):
 .. `mkdir -p *<BDisk directory>*/overlay/etc/systemd/system/getty\@tty1.service.d`
-.. `printf '[Service]\nType=idle\nExecStart=\nExecStart=-/usr/bin/agetty --autologin root --noclear %%I 38400 linux\n' > *<BDisk directory>*/overlay/etc/systemd/system/getty\@tty1.service.d`
+.. `printf '[Service]\nType=idle\nExecStart=\nExecStart=-/usr/bin/agetty --autologin root --noclear %%I 38400 linux\n' > *<BDisk directory>*/overlay/etc/systemd/system/getty\@tty1.service.d/autologin.conf`
 ... (NOTE: This is all one line.)
 
 Remember to also create a https://bdisk.square-r00t.net/#the_code_build_ini_code_file[build.ini file^]. You can find a compatible one https://git.square-r00t.net/AIF-NG/plain/extras/bdisk.build.ini[here^] (but remember to tailor it to your particular paths and needs first!).
@@ -182,7 +182,6 @@ Currently, only one method of logging is enabled, and is always enabled. It can
 == Debugging
 Sometimes it's useful to get a little more information, or to start an installation from within an already-booted environment and you didn't remember (or weren't able to) change the kernel parameters. If this is the case, simply export the `DEBUG` environment variable (it can be set to anything, it doesn't matter) -- if this is done, the arguments will be read from /tmp/cmdline instead. e.g.:
 
- rm -f *
  export DEBUG=true
  cp /proc/cmdline /tmp/.
  chmod 600 /tmp/cmdline
@@ -541,7 +540,7 @@ There are several script types availabe for `execution`. Currently, these are:
 * pkg
 * post
 
-*pre* scripts are run (in numerical `order`) before the disks are even formatted. *pkg* scripts are run (in numerical `order`) right before the <<code_package_code, packages>> are installed (this allows you to configure an <<command, alternate packager>> such as https://aur.archlinux.org/packages/apacman/[apacman^]) -- these are run *inside* the chroot of the new install. *pre* scripts are run inside the chroot like *pkg*, but are executed very last thing, just before the reboot.
+*pre* scripts are run (in numerical `order`) before the disks are even formatted. *pkg* scripts are run (in numerical `order`) right before the <<code_package_code, packages>> are installed (this allows you to configure an <<command, alternate packager>> such as https://aur.archlinux.org/packages/apacman/[apacman^]) -- these are run *inside* the chroot of the new install. *post* scripts are run inside the chroot like *pkg*, but are executed very last thing, just before the reboot.
 
 = Further Information
 Here you will find further info, other resources, and such relating to AIF-NG.

docs/TODO

@@ -1,3 +1,4 @@
+- support Arch Linux ARM?
 - support multiple explicit locales via comma-separated list (see how i handle resolvers)
 - config layout
 -- need to apply defaults and annotate/document
@@ -24,8 +25,8 @@
 	tmp on /mnt/aif/tmp type tmpfs (rw,nosuid,nodev)
 
 DOCUMENTATION: aif-config.py (and note sample json as well)
--finish genXML() or whatever i call it
--add <mirrorlist><mirror><mirror/><mirrorlist/> support- to both the config run and the XML generator
+
+for network configuration, add in support for using a device's MAC address instead of interface name
 
 also create:
 -create boot media with bdisk since default arch doesn't even have python 3