I'm probably asking something that already has been answered somewhere, but i've seen small bits searching through ideas for package management and the like about using strace for determining what files are created/written to during a make install but in all my searching, i havent found any direct implementation ideas outside of using it to determine the dependencies of a package, which isn't much of a concern for me in particular.
I even saw a reference to the idea on linuxquestions where Gerard posted the script he uses(/used) to determine the files written to using a timestamp and find, a common method that always fouls up for me, as i tend to do about 3 to 5 things at a time ... meaning there are many extras tagged as part of the package that actually are in no way related. my question is simply this: how would a person (likely using strace) go about scripting the listing of all files created and modified by a process? and if possible, what those modifications are? i would be interested in writing a hint on this, as soon as i get somewhere. i have no real experience with strace, so i don't yet have any idea what to look for in it's output. the hint would be set up to start the reader at the end of ch5 by walking through building a (if it's even possible) static strace, then using that to document all of the files for each package, then at some point, once the system is far enough along, switching that out to a dynamically linked one for use in the post-"toolbox" system. and would be complete with the scripts to dig through and determine the files for each package and dumping the list to /var/pkg or somewhere similar (better yet, to a variable that defaults to such if unspecified in the environment or the command line). -- Thank You, Joshua M. Murphy -- http://linuxfromscratch.org/mailman/listinfo/lfs-chat FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
