You mean what went wrong before Pharo Snap? I don't have those error messages anymore. When I find the time, I'll try to start over again. Can you help me interpret the messages I do have? Are those Pharo-Snap specific or are those Pharo command line messages? Thanks! - Mark ------ Mark Guzdial, mjguz@umich.edu - Professor of Electrical Engineering and Computer Science, and Engineering Education Research, College of Engineering and Professor of Information, School of Information (courtesy) - Blog: http://computinged.wordpress.com On Thu, May 28, 2020 at 3:20 PM Sven Van Caekenberghe <sven@stfx.eu> wrote:
Hi Mark,
I can't help you with pharo-snap.
But the installation instructions from the Enterprise book, using the command line zero config tools, should still apply and work.
What exactly did go wrong ?
Sven
On 28 May 2020, at 18:23, Mark Guzdial <mjguz@umich.edu> wrote:
Hi everyone,
New here, encouraged (from Discord) to try my questions here.
Iâm struggling to get AWS to run in an Ubuntu AWS instance. I tried following the directions here: https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessfu... but I was getting some error about threads and configurations that I simply didnât understand. Then I tried using Pharo-snap: https://github.com/akgrant43/pharo-snap
Pharo-snap made some of the config problems go away, but when I try starting Pharo on AWS, I get:
ubuntu@ip-172-31-16-17:~$ ./pharo Pharo-sea-roa-sound.image
Usage: [<subcommand>] [--help] [--copyright] [--version] [--list] [ --no-quit ] --help print this help message --copyright print the copyrights --version print the version for the image and the vm --list list a description of all active command line handlers --no-quit keep the image running without activating any other command line handler --deploymentPassword if a password needs to be used by the user to launch the command --readWriteAccessMode, --readOnlyAccessMode, --writeOnlyAccessMode, --disabledAccessMode specify disk access mode, read-write mode as default <subcommand> a valid subcommand in --list
Preference File Modification: --preferences-file load the preferences from the given <FILE> --no-default-preferences do not load any preferences from the default locations
Documentation: A PharoCommandLineHandler handles default command line arguments and options. The PharoCommandLineHandler is activated before all other handlers. It first checks if another handler is available. If so it will activate the found handler.
Clearly, Iâm doing something wrong, but donât know what the next step is, since there isnât an explicit error message. Can someone point a newbie towards the appropriate next steps?
Thanks! - Mark