Tim Mackinnon wrote > FYI: I managed to get it to work - I still get the message about trying to > save the changes file and it not being possible - however my error was not > specifying —no-default-preferences and also around correctly escaping > the command line - the “eval” command is a bit tricky as you need to > escape any “ characters as they are badly interpreted.
The error about saving the changes file comes from the fact that at startup, Pharo tries to open Pharo.changes in read and write mode, which is impossible if you are in a read-only environment. I am working on deploying Pharo in read-only, and it's one of the main problems that shows up during my tests. -- View this message in context: http://forum.world.st/Are-we-able-to-run-pharo-images-in-a-read-only-environment-tp4952705p4952771.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
