|
The way I had in mind, once discovered by dos-fsck, would result in identical copies under different names being created to "fix" what isn't broken.
So might as well just start out with multiple copies.
Then one only must figure out a way to enforce: ldconfig -X ...
Otherwise it would try to replace the copies with the symbolic links.
That sort of thing is usually done by replacing /sbin/ldconfig with a shell script that calls the re-named ldconfig with option -X plus an edited version of the original arguments.
Hmm...
Now we are talking about a change to the filesystem that would break any OTA update when (if) /sbin/ldconfig was ever tested.
Hmm...
Unless we learn to always patch the md5sum manifest file when we change a system file.
Yup, I forsee the need for that bsdiff/bspatch pair of routines mentioned above.
|