|
|
|
|
|
by Alupis
4172 days ago
|
|
I've done something like this before, with my own build scripts. Except I was running as root (a requirement for some parts of the build). Part of the scripts installed a bunch of files into what was supposed to be a fakeroot, however I did not have bash's 'set -u' configured and an incorrectly spelled path variable was null, meaning something like: "${FAKEROOT}/etc" was translated into "/etc". Before I realized it, it had clobbered most of my /etc directory. When the build failed, I was puzzled. I only noticed there was an issue when I opened a new shell and instead of seeing "myuser@host ~]#" I got "noname@unknown ~]#". Uh oh... Needless to say I know do my development of those scripts from within a VM. |
|