I would try to run pharo through strace (http://linux.die.net/man/1/strace <http://linux.die.net/man/1/strace>). This way, you will probably see a system call trying to write to a file in read-only mode.
Hope this helps. Christophe > Le 12 juil. 2016 à 15:33, Valentin Ryckewaert <valentin.ryckewa...@gmail.com> > a écrit : > > Hello everyone, > > I'm currently working on the project file policy and I'm having a problem > that I don't understand > > I import my code, configure my image as readOnly (Pharo won't try to write on > changesFiles,source,image....), set the folder of the image in readonly and > try to open the image again and it's not possible, I don't get any stacktrace > so it's hard to understand the problem. > > PS : If we set back the folder in write mode, it's possible again to open the > image again. > > Here is the code to reproduce the bug, could someone give me a clue please? > > sudo rm -r testPharo > mkdir testPharo > cd testPharo > > echo "Metacello new > smalltalkhubUser: 'Uryon' project: 'Coral'; > configuration: 'Coral'; > version: #development; > onConflictUseIncoming; > load. > SmalltalkImage configureSystemAsReadonlyAndQuit:true > " >> load.st <http://load.st/> > > mkdir coral > cd coral > curl get.pharo.org/alpha <http://get.pharo.org/alpha> | bash > curl get.pharo.org/vm60 <http://get.pharo.org/vm60> | bash > pharo-vm/pharo Pharo.image ../load.st <http://load.st/> > cd .. > chmod -R -w coral > coral/pharo-vm/pharo coral/Pharo.image >
