On the tail end of part III we were awaitin' the bootstrapper to finish its long and arduous whizzing.
I woke to find that a lot of kernel configuration awaited me as the result of "professional" negligence somewhere deep upstream. asciilifeform kindly provided a standard configuration to work against, so I set myself to y-in', n-in, and occasionally m-in'.
During which my hand-eye coordination got a little wobbly, and I killed the entire run with an unhappy hit of ctrl + c on the wrong keyboard. Because totally, this failure mode was thought about at some point, and it was decided in a stroke of genius that this innocuous operation oughta be capable of murdering arbitrary layers of a process.
Anyway, I proved to myself the value of the script produced in part III, as I had to run it yet again. I can't describe the second kernel configuration walkthrough as anything but pedantic white-knuckling. I kept a list of what trinque's kernel asked for that asciilifeform's configuration file didn't know about; interested parties can grab it here.
Sadly enough, I find that at the end of the config q&a, and hence the end of the bootstrapper script, I'm still left without a genesis with which to compare trinque's signature. Given which vdiff for instance shows vdiff in my path, I'm at a loss as to why no patch was produced. I also note that I lack even a cuntoo/portage directory.
The next steps being review of the script's record during the run, and deferment to the wisdom of the forum, I ask you: wtf?
No it didn't.
test one.
and test two.
[...] other writings on the matter, such as Lobbes', Mod6's (archived) and Hanbot's Cuntoo [...]