On Mon, Nov 20, 2017 at 02:01:56PM -0700, Theo de Raadt wrote: > If someone wants to solve this fully there have been some proposals > for keeping track of the instruction sequence, and attempting to > reapply it upon each relink in the build directory. There just hasn't > been any scripting changes to do that from anyone, and it isn't on my > radar as important.
Ah, rather than make binary changes to the object files that get linked, just redo the changes to the resultant kernel binary every time it is generated. That's definitely simpler to do with the existing tools. I see someone made a suggestion that you replied to with a classic "where's the patch" :), I don't think he was suggesting someone else do it but more looking for guidance on what you'd considerable acceptable before spending time on it. For example, would the basic "user manually constructs a text file with config commands by hand that then just gets passed to config on stdin" approach he mentioned be good enough to commit? Or would you want something more integrated into config where it would have a new command that would generate a file based on the current session, and a new option to process changes from a file rather than interactively? It looks like it would be difficult to detect errors in the first scenario, and I don't know if that would be an issue. Thanks...
