diff --git a/software/Versioned config files.md b/software/Versioned config files.md
index 910f14e..1df878f 100644
--- a/software/Versioned config files.md	
+++ b/software/Versioned config files.md	
@@ -1,6 +1,11 @@
 ## Solutions 
-- Create a directory, eg `/etc/config` and store all of your config files there, then use a makefile to automatically generate symlinks and install them in the appropriate locations. A command is also created for removing said symlinks. (<https://forums.freebsd.org/threads/version-control-for-configuration-files.70312/>)
-- Using a solution like zfs/btrfs
+- Create a directory, eg `/etc/config` and store all of your config files there, then use a makefile to automatically generate symlinks and install them in the appropriate locations. A command is also created for removing said symlinks. (https://forums.freebsd.org/threads/version-control-for-configuration-files.70312/)
+	- I like this so far, it seems like one of the better options.
+- Using a filesystem that supports snapshots like zfs/btrfs and then creating snapshots (https://forums.FreeBSD.org/threads/version-control-for-configuration-files.70312/post-423330).
+	- I don't like this very much, it depends too much on OS specific configuration and doesn't seem like it'd be as easily portable between machines.
+- Using a configuration management system like Ansible, Chef, or Puppet (<https://www.dolthub.com/blog/2023-12-12-configuration-version-control/#isnt-this-just-configuration-management>)
+	- I feel like this would require a fair bit of initial setup but it seems robust
+- Using a database like 
 
 ## Notes
 I think one major issue with storing configs in a solution like git, is that you need to remember to push changes after every single config change. Maybe a cronjob could be configured to commit daily/weekly?