update readme

diff --git a/README b/README
index 3cd36872184e7663bd820dcc03b1654b825058c1..41e942a2a5a54554642a9d8c8c479abdc85a17ad 100644 (file)
--- a/README
+++ b/README
@@ -1,6 +1,40 @@
 Scripts to setup distros how I like
 
-Initial os install is also automated using a separate repo callied
-"fai", also at iankelling.org/git. It's not meant for other people to
-run verbatum, but for them to read and copy the good parts. It has
-dependencies on other repos at https://iankelling.org/git.
+Initial os install is also automated using a separate repo called
+automated-distro-installer, also at iankelling.org/git.
+
+This is not meant for other people to run verbatum, but for them to read
+and copy the good parts. It has dependencies on other repos at
+https://iankelling.org/git.
+
+
+The main thing missing is any automation for the directory structure
+those repos live in. So you would need to lookout for paths starting with
+/a and adjust them.
+
+Background: reasoning behind using /a: The home directory is typically
+used for local software development, but I use paths like /a instead,
+for the following reasons:
+
+1. I want to run code directly from where I work on it, instead of
+always having to create and use some install process. If that code is in
+a home directory, and you want to run it as root (especially in contexts
+where SUDO_USER is not set, like cron/systemd), you have to hardcode the
+username for /home/username, or create some install process where that
+username is saved somewhere, and then you are stuck with a single
+username. If it ever got packaged for a gnu/linux distro, it would rely
+on a hardcoded path with no username in it, so let's just do that.
+
+2. The home directory is inconvenient. It's filled with a bunch of junk
+you don't care about, which makes directory listing horible, makes it so
+you can't back it up easily (for example, gvfs mountpoint in it breaks
+lots of things), and has things you don't want to backup. So, you could
+use a subdirectory. But typing /s is much faster than ~/s and in every
+root context, /home/username/s.
+
+With that established, some more details of what directories I use. I
+have a data filesystem, and if the system has ssd & hdd, I have 2 data
+filesystems. I mount them to single letter root directories, and then
+split them into data I do and don't mind being public, then bind mount
+them to other single letter directories. When I'm working on something a
+lot, I symlink it to another top level directory.
\ No newline at end of file