Now it seems to work,
I followed you instruction from the first mail and just added another line
to the load.st
(unset option to inform about read only changes files)
Metacello new
smalltalkhubUser: 'Uryon' project: 'Coral';
configuration: 'Coral';
version: #development;
onConflictUseIncoming;
load.
PharoFilesOpener default unsetInformAboutReadOnlyChanges.
SmalltalkImage configureSystemAsReadonlyAndQuit:true
2016-07-19 0:27 GMT+02:00 Valentin Ryckewaert <valentin.ryckewa...@gmail.com
>:
> We tried to put it in a file, print in in stdout, put it as an display in
> the image....
>
> 2016-07-18 21:48 GMT+02:00 Nicolai Hess <nicolaih...@gmail.com>:
>
>>
>>
>> 2016-07-18 14:36 GMT+02:00 Valentin Ryckewaert <
>> valentin.ryckewa...@gmail.com>:
>>
>>> Hello,
>>>
>>> with Pavel we tried to print with a lot of methods but it didn't work,
>>> i'm searching the source of the problem manually.
>>>
>>
>> What do you mean witth:
>> "tried to print with a lot of methods" ?
>>
>> You can not use stdout to print when doing image shutdown and restart,
>> because all file streams will be closed during the shutdown (see session
>> manager).
>> If you want to use stdout to print log messages (right after image
>> startup), you need to make sure that the stdout/err stream are already
>> recreated.
>> (And for example, reinitialize Coral, if coral has reference to the (old)
>> closed filestream.
>>
>>
>>
>>
>>>
>>> 2016-07-18 14:32 GMT+02:00 stepharo <steph...@free.fr>:
>>>
>>>> Thanks for the suggestion. It is probably the case.
>>>>
>>>> Le 17/7/16 à 23:27, Nicolai Hess a écrit :
>>>>
>>>> Hi Valentin, Ithink you can not print to stdout during shutdown and
>>>> restart.
>>>> It will end in a Loop of writing to stdout, throwing an exceptions
>>>> because it can not write and trying to log the error on stdout, throwing an
>>>> error...
>>>>
>>>> Am 17.07.2016 18:36 schrieb "Valentin Ryckewaert" <
>>>> valentin.ryckewa...@gmail.com>:
>>>>
>>>>> i will do it tomorrow.
>>>>>
>>>>> 2016-07-17 17:23 GMT+02:00 stepharo <steph...@free.fr>:
>>>>>
>>>>>> did you try to solution proposed?
>>>>>>
>>>>>> Stef
>>>>>>
>>>>>> Le 17/7/16 à 16:22, Valentin Ryckewaert a écrit :
>>>>>>
>>>>>> Hello Stef,
>>>>>>
>>>>>> no i'm still on it :(
>>>>>> I'm going to test every code I modified
>>>>>>
>>>>>> Valentin
>>>>>>
>>>>>> 2016-07-17 15:23 GMT+02:00 stepharo <steph...@free.fr>:
>>>>>>
>>>>>>> HI valentin
>>>>>>>
>>>>>>>
>>>>>>> did you solve your problem?
>>>>>>>
>>>>>>>
>>>>>>> Stef
>>>>>>>
>>>>>>> Le 12/7/16 à 15:33, Valentin Ryckewaert 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
>>>>>>>
>>>>>>> mkdir coral
>>>>>>> cd coral
>>>>>>> curl get.pharo.org/alpha | bash
>>>>>>> curl get.pharo.org/vm60 | bash
>>>>>>> pharo-vm/pharo Pharo.image ../load.st
>>>>>>> cd ..
>>>>>>> chmod -R -w coral
>>>>>>> coral/pharo-vm/pharo coral/Pharo.image
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
