minor bug fix
[distro-setup] / README
1 ~4k loc bash, configs for my computers
2
3 Initial os install is also automated using a separate repo called
4 automated-distro-installer, also at iankelling.org/git. Beyond the
5 initial bare os, the rest is automated from scripts in this repo.
6
7 This is not meant for other people to run verbatum, but for them to read
8 and copy the good parts. It has dependencies on other repos at
9 https://iankelling.org/git.
10
11 The main thing missing for someone else to use things is the expected
12 location of repos in the filesystem. So you would need to lookout for
13 paths starting with /a and adjust them.
14
15 Background: reasoning behind using /a: The home directory is typically
16 used for local software development, but I use paths like /a instead,
17 for the following reasons:
18
19 1. I want to run code directly from where I work on it, instead of
20 always having to create and use some install process. If that code is in
21 a home directory, and you want to run it as root (especially in contexts
22 where SUDO_USER is not set, like cron/systemd), you have to hardcode the
23 username for /home/username, or create some install process where that
24 username is saved somewhere, and then you are stuck with a single
25 username. If it ever got packaged for a gnu/linux distro, it would rely
26 on a hardcoded path with no username in it, so let's just do that.
27
28 2. The home directory is inconvenient. It's filled with a bunch of junk
29 you don't care about, which makes directory listing horrible, makes it so
30 you can't back it up easily (for example, gvfs mountpoint in it breaks
31 lots of things), and has things you don't want to backup. So, you could
32 use a subdirectory. But typing /s is much faster than ~/s and in every
33 root context, /home/username/s.
34
35 Please email me if you have a patches, bugs, feedback, or republish this
36 somewhere else: Ian Kelling <ian@iankelling.org>.