For those who are having permissions problems, here is what iLLNESS said:
Originally Posted by iLLNESSwhy does a game that was installed/updated/saved in hermes have issues with pl3... but when the same data was installed/updated/saved/etc in pl3 work with hermes? start from the ground up and not from the top down and you might understand how its dirty. ultimately whats determined as clean is something that becomes compatible with other payloads... something hermes doesnt seem to be right now. using hermes before pl3 is the issue at stake right now. why is this?
you can jump ship on the hermes side and say its clean, or you can be neutral about it, or even be on pl3 side but what remains is what we can see.
what i see is the games i had problems with using pl3 were resolved by deleting any data that was created using hermesv4b payload. interestingly enough, when i installed this data using pl3 it still worked with hermes afterwards. like evilsperm said, its like or is a linux file system. it has permissions just the same. ask anyone who runs a linux based os how clean running everything as root is.
here's a simple test you can perform.
-boot hermes payload. load a game like MOH. install all updates... quit game. ftp to ps3 and try to view the updates icon. you will be able to view it.
-boot latest pl3 payload. ftp to ps3 and try to view the updates icon. you will be not able to view it due to file permissions.
-delete game updates. boot moh with pl3. update game. ftp to ps3 and try to view the updates icon. you will be able to view it.
-boot hermes payload. ftp into ps3 and try to view the updates icon. you will be able to view it.
hermes is setting file permissions HIGHER then the user who is logged in to the ps3 for things like game updates. why is the file permission higher? who the heck knows. all i know is these file permissions are NOT an issue if your using PL3 from the ground up.