Am I really expected to rewrite all of these, or is the change in semantics
actually a bug?

buildsistareader64image.sh:echo $VM trunksista64reader.image -- LoadFFI.st
buildsistareader64image.sh:$VM trunksista64reader.image -- LoadFFI.st
buildsistareader64image.sh:echo $VM trunksista64reader.image --
LoadReader.st
buildsistareader64image.sh:$VM trunksista64reader.image -- LoadReader.st
buildsistareader64image.sh:echo $VM trunksista64reader.image --
StartReader.st
buildsistareader64image.sh:$VM trunksista64reader.image -- StartReader.st
buildsistareaderimage.sh:echo $VM sistareader.image -- LoadSistaSupport.st
buildsistareaderimage.sh:$VM sistareader.image -- LoadSistaSupport.st
buildsistareaderimage.sh:echo $VM sistareader.image -- LoadReader.st
buildsistareaderimage.sh:$VM sistareader.image -- LoadReader.st
buildsistareaderimage.sh:echo $VM sistareader.image -- StartReader.st
buildsistareaderimage.sh:$VM sistareader.image -- StartReader.st
buildspurtrunk64image.sh:echo $VM SpurVMMaker.image --
BuildSpurTrunk64Image.st
buildspurtrunk64image.sh:$VM SpurVMMaker.image -- BuildSpurTrunk64Image.st
buildspurtrunkreader64image.sh: echo $VM spurreader-64.image -- LoadFFI.st
buildspurtrunkreader64image.sh: $VM spurreader-64.image -- LoadFFI.st
buildspurtrunkreader64image.sh:echo $VM spurreader-64.image -- LoadReader.st
buildspurtrunkreader64image.sh:$VM spurreader-64.image -- LoadReader.st
buildspurtrunkreader64image.sh:echo $VM spurreader-64.image --
StartReader.st
buildspurtrunkreader64image.sh:$VM spurreader-64.image -- StartReader.st
buildspurtrunkreaderimage.sh: echo $VM spurreader.image -- LoadFFI.st
buildspurtrunkreaderimage.sh: $VM spurreader.image -- LoadFFI.st
buildspurtrunkreaderimage.sh:echo $VM spurreader.image -- LoadReader.st
buildspurtrunkreaderimage.sh:$VM spurreader.image -- LoadReader.st
buildspurtrunkreaderimage.sh:echo $VM spurreader.image -- StartReader.st
buildspurtrunkreaderimage.sh:$VM spurreader.image -- StartReader.st
buildspurtrunkvmmaker64image.sh:echo $VM Spur64VMMaker.image --
BuildSqueakSpurTrunkVMMakerImage.st
buildspurtrunkvmmaker64image.sh:$VM Spur64VMMaker.image --
BuildSqueakSpurTrunkVMMakerImage.st
buildspurtrunkvmmakerimage.sh:echo $VM SpurVMMaker.image --
BuildSqueakSpurTrunkVMMakerImage.st
buildspurtrunkvmmakerimage.sh:$VM SpurVMMaker.image --
BuildSqueakSpurTrunkVMMakerImage.st
envvars.sh:if unzip --help >/dev/null; then
getsqueak50.sh: if unzip --help >/dev/null; then
updatespur64SistaV1image.sh: echo $VM $BASESISTA64.image --
NukePreferenceWizardMorph.st
updatespur64SistaV1image.sh: $VM $BASESISTA64.image --
NukePreferenceWizardMorph.st
updatespur64SistaV1image.sh: echo $VM $BASESISTA64.image -- SaveAsSista.st
updatespur64SistaV1image.sh: $VM $BASESISTA64.image -- SaveAsSista.st
updatespur64SistaV1image.sh: echo $VM $BASESISTA64.image --
NukePreferenceWizardMorph.st
updatespur64SistaV1image.sh: $VM $BASESISTA64.image --
NukePreferenceWizardMorph.st
updatespur64SistaV1image.sh:echo $VM $BASESISTA64.image --
UpdateSqueakTrunkImage.st
updatespur64SistaV1image.sh:$VM $BASESISTA64.image --
UpdateSqueakTrunkImage.st
updatespur64image.sh: echo $VM $BASE64.image -- NukePreferenceWizardMorph.st
updatespur64image.sh: $VM $BASE64.image -- NukePreferenceWizardMorph.st
updatespur64image.sh:echo $VM $BASE64.image -- UpdateSqueakTrunkImage.st
updatespur64image.sh:$VM $BASE64.image -- UpdateSqueakTrunkImage.st
updatespurimage.sh: echo $VM $BASE.image -- NukePreferenceWizardMorph.st
updatespurimage.sh: $VM $BASE.image -- NukePreferenceWizardMorph.st
updatespurimage.sh:echo $VM $BASE.image -- UpdateSqueakTrunkImage.st
updatespurimage.sh:$VM $BASE.image -- UpdateSqueakTrunkImage.st
updatevmmakerimage.sh:echo $VM SpurVMMaker.image --
UpdateSqueakTrunkImage.st
updatevmmakerimage.sh:$VM SpurVMMaker.image -- UpdateSqueakTrunkImage.st

On Thu, Jul 21, 2022 at 6:23 PM Eliot Miranda <eliot.miranda at gmail.com>
wrote:

> Hi All,
>
>     I'm trying ot update the VMMaker image build scripts. I've got as far
> as downloading the latest 6.x image and VM (much easier now; thanks to
> everyone who has made the github pages easier to navigate!!).
>
> How do I launch a trunk6 image with a script so that the system is running
> headful and one can see it make progress?
>
> I am launching with this on MacOS: and I get a headless blank screen that
> appears to be 640x480, quite different to the normal startup showing the
> configuration wizard I get f I launch without the arguments:
>
> ./Squeak.app/Contents/MacOS/Squeak trunk6-64.image
> -- UpdateSqueakTrunkImage.st
>
> where trunk6-64.image is a clone of e.g. Squeak6.0-22104-64bit.image
>
> I've tried
>     ./Squeak.app/Contents/MacOS/Squeak trunk6-64.image -- --filein
> UpdateSqueakTrunkImage.st    ./Squeak.app/Contents/MacOS/Squeak
> trunk6-64.image --filein UpdateSqueakTrunkImage.st
> etc, but get the 640x480 grey screen image.
> _,,,^..^,,,_
> best, Eliot
>


-- 
_,,,^..^,,,_
best, Eliot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20220721/16d1c4ca/attachment.html>