In the mist of refactoring the code to use only fileXio, I found that uLaunchELF will change the timestamps for files after copying. However, the code for doing so for a PFS destination was commented out, saying that it doesn't work.
So did it never work? Does anyone know what actually happens? Or was it already fixed, but just not enabled within uLaunchELF?
Right now, I have re-enabled the code. If it is a problem with PFS, then PFS should be looked at. Or if it wasn't ever a feature that PFS was meant to have (and it also comes with some ill effects), then it should be re-disabled within uLaunchELF with the appropriate comments.
No, it did not. The workaround was to work around a glitch in PFS. The wrong cache entry was being freed, which resulted in a cache coherency problem. The issue has been resolved.
In the mist of refactoring the code to use only fileXio, I found that uLaunchELF will change the timestamps for files after copying. However, the code for doing so for a PFS destination was commented out, saying that it doesn't work.
So did it never work? Does anyone know what actually happens? Or was it already fixed, but just not enabled within uLaunchELF? Right now, I have re-enabled the code. If it is a problem with PFS, then PFS should be looked at. Or if it wasn't ever a feature that PFS was meant to have (and it also comes with some ill effects), then it should be re-disabled within uLaunchELF with the appropriate comments.