March 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] PharoNOS

by Damien Pollet

Is it specific to KVM, or is it possible to run it on top of different hypervisors? E.g. is it possible to make a demo VirtualBox image, or to launch PharoNOS as a Docker container? On 19 March 2017 at 15:33, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hi. > > How difficult it would be to support ARM processor? > > 2017-03-19 0:30 GMT+01:00 jan.struz <public+pharo(a)struz.cz>: > >> Hi, >> I successfully ported SqueakNOS to Pharo, and want to share it with you! >> It works with Pharo 4.0 image, networking included, ping works! >> >> *What is different:* >> - I use my own CMake build file, with "out-of-tree" build support, >> instead of "build.xyz" directories inside source tree + some template >> scripts to build any VM type, but it is not complete... >> - I use MUSL <http://www.musl-libc.org/> instead of GlibC, >> cross-compiling GlibC statically on 64bit for 32bit seems impossible, but >> anyway I use 32bit environment to build it >> - It works with pre-opensmalltalk-vm migration directory structure, so >> the "sync" with latest trunk remains #TODO, or maybe start a new branch >> again from the latest upstream commit should work too >> - freetype is included, but will not load any fonts, since the filesystem >> driver is image-side... so you will need to make new fonts embedded, if you >> want them >> - known issues: image snapshot and fileout are not working, current >> date+time hacked to make fat32 timestamps work >> - revision needed: timer (heartbeat) vs. GC vs. interrupts enable/disable >> - there are even some hacks to image-side methods >> >> *PharoNOS platform directory sources: [pharonos branch]* >> SRC: https://gitlab.com/johnnyzz/pharonos >> >> *VM sources: [dev branch]* >> SRC: https://gitlab.com/johnnyzz/pharo-vm >> - added platform directory, build scripts and CMake templates >> - added VMMaker configs >> >> *Build Environment (32bit) - Docker image repository, with CI:* >> https://gitlab.com/johnnyzz/dev-build >> >> *PharoNOS CI (uses previous Docker image):* >> CI: https://gitlab.com/johnnyzz/pharo-nos-build >> >> *How to run it:* >> You can download fresh disk image from CI and then run: >> (sudo) kvm -hda build/NOS.img -enable-kvm -cpu kvm32 -vga qxl -m 256 >> -netdev tap,id=user.3,ifname=tap2,vhost=on -net >> nic,model=rtl8139,netdev=user.3 -global isa-fdc.driveA= -serial stdio >> >> *One more thing:* >> Statically linked Pharo Spur32 (headless) VM, with only one dependency - >> Linux kernel: >> CI: https://gitlab.com/johnnyzz/pharo-build-static >> Size: 2,4MB (too big?, but Freetype included too!) >> >> enjoy >> >> Jan >> Save The World! >> >> ------------------------------ >> View this message in context: [ANN] PharoNOS >> <http://forum.world.st/ANN-PharoNOS-tp4939247.html> >> Sent from the Pharo Smalltalk Developers mailing list archive >> <http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html> at >> Nabble.com. >> > > -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

March 19, 2017

Re: [Pharo-dev] platforms/Nopsys submodule

by Ben Coman

On Sat, Mar 18, 2017 at 11:24 PM, Guido Chari <charig(a)gmail.com> wrote: > Hi, > > We didn't expect to be found yet :). > haHaaa!! *grin* the many eyeballs of opensource strikes again! Hopefully there is some benefit in my poking my nose to learn of Jan's work. Release early, Release often is the mantra on the day. btw, This history page initially confused me... https://gitlab.com/johnnyzz/pharonos/network/pharonos The top five commits (Oct 25 - Nov 3) are Jan's 2016 work. Commit six (Apr 7) and lower is your work from 2011. Its a pain there is nothing to indicate such a jump in time. cheers -ben > But well...we are actually working on a second revival of the SqueakNOS > project. Hope to give news in the mailing list soon, but we are still far > from having something working with all the new stuff. > > Concerning submodules, yes there are plenty of arguments for and against. > I've been using them successfully in some projects depending on the > Truffle/Graal platform. Nonetheless, in case we managed to make progress > and the community is interested on the results, for sure we will be open to > discuss about this. > > Best, > Guido. > > 2017-03-18 10:53 GMT-03:00 Ben Coman <btc(a)openinworld.com>: > >> In the network graph hovering over charig/2-March commit I see a new >> platform Nopsys added for SqueakNOS. >> [A] https://github.com/OpenSmalltalk/opensmalltalk-vm/network >> >> Thats cool !!! It'll be great to see this work with OpenSmalltalk. >> However I notice its been added as a submodule. >> [B] https://github.com/charig/opensmalltalk-vm/commit/2bd87b525b >> 6b46439c90506c0a47e17ea1d5ac93 >> >> Submodules bring additional complexity, so I thought there should be >> some discussion on this topic. >> Here are a couple of balanced introductions to submodules... >> [C] http://www.catalyst-au.net/blog/git-submodule-misunderstood- >> beast-or-remorseless-slavering-monster >> [D] https://www.philosophicalhacker.com/post/using-git-submodule >> s-effectively/ >> >> And a couple of cautions about using them... >> [E] http://slopjong.de/2013/06/04/git-why-submodules-are-evil/ >> [F] https://rufflewind.com/2017-02-21/quirks-with-submodules >> >> >> Guido & Javier, >> Have you used submodules successfully elsewhere? >> Could you discuss your strategy using a submodule for the platform >> code rather than adding directly into the opensmalltalk-vm repository? >> >> I see your parent repository includes opensmalltalk-vm as a submodule >> similar to how I *thought* Pharo was doing it, but wait on comment >> from Esteban. . >> [G] https://github.com/charig/Nopsys >> [H] https://github.com/charig/Nopsys/blob/master/.gitmodules >> So it seems platforms/Nopsys is a sub-sub-module. >> >> cheers -ben >> >> >

March 19, 2017

Re: [Pharo-dev] [ANN] PharoNOS

by Denis Kudriashov

Hi. How difficult it would be to support ARM processor? 2017-03-19 0:30 GMT+01:00 jan.struz <public+pharo(a)struz.cz>: > Hi, > I successfully ported SqueakNOS to Pharo, and want to share it with you! > It works with Pharo 4.0 image, networking included, ping works! > > *What is different:* > - I use my own CMake build file, with "out-of-tree" build support, instead > of "build.xyz" directories inside source tree + some template scripts to > build any VM type, but it is not complete... > - I use MUSL <http://www.musl-libc.org/> instead of GlibC, > cross-compiling GlibC statically on 64bit for 32bit seems impossible, but > anyway I use 32bit environment to build it > - It works with pre-opensmalltalk-vm migration directory structure, so the > "sync" with latest trunk remains #TODO, or maybe start a new branch again > from the latest upstream commit should work too > - freetype is included, but will not load any fonts, since the filesystem > driver is image-side... so you will need to make new fonts embedded, if you > want them > - known issues: image snapshot and fileout are not working, current > date+time hacked to make fat32 timestamps work > - revision needed: timer (heartbeat) vs. GC vs. interrupts enable/disable > - there are even some hacks to image-side methods > > *PharoNOS platform directory sources: [pharonos branch]* > SRC: https://gitlab.com/johnnyzz/pharonos > > *VM sources: [dev branch]* > SRC: https://gitlab.com/johnnyzz/pharo-vm > - added platform directory, build scripts and CMake templates > - added VMMaker configs > > *Build Environment (32bit) - Docker image repository, with CI:* > https://gitlab.com/johnnyzz/dev-build > > *PharoNOS CI (uses previous Docker image):* > CI: https://gitlab.com/johnnyzz/pharo-nos-build > > *How to run it:* > You can download fresh disk image from CI and then run: > (sudo) kvm -hda build/NOS.img -enable-kvm -cpu kvm32 -vga qxl -m 256 > -netdev tap,id=user.3,ifname=tap2,vhost=on -net > nic,model=rtl8139,netdev=user.3 -global isa-fdc.driveA= -serial stdio > > *One more thing:* > Statically linked Pharo Spur32 (headless) VM, with only one dependency - > Linux kernel: > CI: https://gitlab.com/johnnyzz/pharo-build-static > Size: 2,4MB (too big?, but Freetype included too!) > > enjoy > > Jan > Save The World! > > ------------------------------ > View this message in context: [ANN] PharoNOS > <http://forum.world.st/ANN-PharoNOS-tp4939247.html> > Sent from the Pharo Smalltalk Developers mailing list archive > <http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html> at > Nabble.com. >

March 19, 2017

Re: [Pharo-dev] [ANN] PharoNOS

by stepharong

Thanks Jan This is super coooooooooooooooooooooooooooooooooooooooooooooooooool :) Since we are bootstrapping a kernel for Pharo70. And we can really get much smaller images in the future, let us know if you want a special image. Jonathan is working on making sure than other people than guille can use the process. Stef On Sun, 19 Mar 2017 00:30:40 +0100, jan.struz <public+pharo(a)struz.cz> wrote: > Hi, > I successfully ported SqueakNOS to Pharo, and want to share it with you! > It works with Pharo 4.0 image, networking included, ping works! > > What is different: > - I use my own CMake build file, with "out-of-tree" build support, > instead of "build.xyz" directories inside source tree + some template > scripts to build any VM type, but it is not complete... > - I use MUSL instead of GlibC, cross-compiling GlibC statically on 64bit > for 32bit seems impossible, but anyway I use 32bit environment to build > it > - It works with pre-opensmalltalk-vm migration directory structure, so > the "sync" with latest trunk remains #TODO, or maybe start a new branch > again from the latest upstream commit should work >too > - freetype is included, but will not load any fonts, since the > filesystem driver is image-side... so you will need to make new fonts > embedded, if you want them > - known issues: image snapshot and fileout are not working, current > date+time hacked to make fat32 timestamps work > - revision needed: timer (heartbeat) vs. GC vs. interrupts enable/disable > - there are even some hacks to image-side methods > > PharoNOS platform directory sources: [pharonos branch] > SRC: https://gitlab.com/johnnyzz/pharonos > > VM sources: [dev branch] > SRC: https://gitlab.com/johnnyzz/pharo-vm > - added platform directory, build scripts and CMake templates > - added VMMaker configs > > Build Environment (32bit) - Docker image repository, with CI: > https://gitlab.com/johnnyzz/dev-build > > PharoNOS CI (uses previous Docker image): > CI: https://gitlab.com/johnnyzz/pharo-nos-build > > How to run it: > You can download fresh disk image from CI and then run: > (sudo) kvm -hda build/NOS.img -enable-kvm -cpu kvm32 -vga qxl -m 256 > -netdev tap,id=user.3,ifname=tap2,vhost=on -net > nic,model=rtl8139,netdev=user.3 -global isa-fdc.driveA= -serial stdio > > One more thing: > Statically linked Pharo Spur32 (headless) VM, with only one dependency - > Linux kernel: > CI: https://gitlab.com/johnnyzz/pharo-build-static > Size: 2,4MB (too big?, but Freetype included too!) > > enjoy > > Jan > Save The World! > View this message in context: [ANN] PharoNOS > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. -- Using Opera's mail client: http://www.opera.com/mail/

March 19, 2017

Re: [Pharo-dev] [ANN] PharoNOS

by jan.struz

I forgot, the source points to repository @ smalltalkhub http://smalltalkhub.com/#!/~JanStruz/PharoNOS/ ----- Save The World! -- View this message in context: http://forum.world.st/ANN-PharoNOS-tp4939247p4939249.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 18, 2017

Re: [Pharo-dev] platforms/Nopsys submodule

by jan.struz

Announcement here: http://forum.world.st/ANN-PharoNOS-td4939247.html <http://forum.world.st/ANN-PharoNOS-td4939247.html> ----- Save The World! -- View this message in context: http://forum.world.st/platforms-Nopsys-submodule-tp4939215p4939248.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 18, 2017

[ANN] PharoNOS

by jan.struz

Hi, I successfully ported SqueakNOS to Pharo, and want to share it with you! It works with Pharo 4.0 image, networking included, ping works! What is different: - I use my own CMake build file, with "out-of-tree" build support, instead of "build.xyz" directories inside source tree + some template scripts to build any VM type, but it is not complete... - I use MUSL <http://www.musl-libc.org/> instead of GlibC, cross-compiling GlibC statically on 64bit for 32bit seems impossible, but anyway I use 32bit environment to build it - It works with pre-opensmalltalk-vm migration directory structure, so the "sync" with latest trunk remains #TODO, or maybe start a new branch again from the latest upstream commit should work too - freetype is included, but will not load any fonts, since the filesystem driver is image-side... so you will need to make new fonts embedded, if you want them - known issues: image snapshot and fileout are not working, current date+time hacked to make fat32 timestamps work - revision needed: timer (heartbeat) vs. GC vs. interrupts enable/disable - there are even some hacks to image-side methods PharoNOS platform directory sources: [pharonos branch] SRC: https://gitlab.com/johnnyzz/pharonos VM sources: [dev branch] SRC: https://gitlab.com/johnnyzz/pharo-vm - added platform directory, build scripts and CMake templates - added VMMaker configs Build Environment (32bit) - Docker image repository, with CI: https://gitlab.com/johnnyzz/dev-build PharoNOS CI (uses previous Docker image): CI: https://gitlab.com/johnnyzz/pharo-nos-build How to run it: You can download fresh disk image from CI and then run: (sudo) kvm -hda build/NOS.img -enable-kvm -cpu kvm32 -vga qxl -m 256 -netdev tap,id=user.3,ifname=tap2,vhost=on -net nic,model=rtl8139,netdev=user.3 -global isa-fdc.driveA= -serial stdio One more thing: Statically linked Pharo Spur32 (headless) VM, with only one dependency - Linux kernel: CI: https://gitlab.com/johnnyzz/pharo-build-static Size: 2,4MB (too big?, but Freetype included too!) enjoy Jan ----- Save The World! -- View this message in context: http://forum.world.st/ANN-PharoNOS-tp4939247.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 18, 2017

Re: [Pharo-dev] platforms/Nopsys submodule

by Guido Chari

Great!!!! Where can we find the code for building the image? 2017-03-18 13:03 GMT-03:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > Hi jan > > this is super cool. > Now with the bootstrap of the system as well as the possibility using > guille approach to generate smaller image this open a lot of space. > > stef > > > On Sat, Mar 18, 2017 at 4:53 PM, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > >> This is so cool!!! >> >> 2017-03-18 16:30 GMT+01:00 jan.struz <public+pharo(a)struz.cz>: >> >>> Hi, >>> please stop for a while... I want to show you something... >>> >>> >>> >>> Actually it is already done... >>> Save The World! >>> >>> ------------------------------ >>> View this message in context: Re: platforms/Nopsys submodule >>> <http://forum.world.st/platforms-Nopsys-submodule-tp4939215p4939230.html> >>> Sent from the Pharo Smalltalk Developers mailing list archive >>> <http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html> at >>> Nabble.com. >>> >> >> >

March 18, 2017

Re: [Pharo-dev] about propertyAt: and others

by Stephane Ducasse

It is a lib to manage configuration like the one on pillar. Now cocoon is using magritte and this is a bit too much for my taste so I'm doing one iteration to produce a new lib where validation and runtime can be separated. Stef On Sat, Mar 18, 2017 at 3:44 PM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > What is Cocoon? > > Phil > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. > www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > <#m_-2178890555753590694_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > On Sat, Mar 18, 2017 at 1:18 PM, stepharong <stepharong(a)free.fr> wrote: > >> Hi >> >> I'm looking at cocoon and other property systems. I would like to get a >> nice library once for all. >> I want to also revisit Artefact stylesheets. >> >> I'm checking the semantics regarding the lookup of a property in a parent >> when it is not found in the receiver. >> >> I have the impression that when there is a parent access and modification >> should modify the same object: i.e., the parent if the key is found in the >> parent or the child if the property is found in the child. >> >> >> in cocoon we have a mix of the two semantics and I would like to get your >> feel about it. >> >> propertyAt: aKey >> "Answer the value of the property ==aKey==, raises an error if >> the property doesn't exist." >> >> ^ self propertyAt: aKey ifAbsent: [ >> self hasParent >> ifTrue: [ self parent propertyAt: aKey ] >> ifFalse: [self errorPropertyNotFound: aKey ]] >> >> propertyAt: aKey default: aBlock >> "Answer the value of ==aKey==. If the key have no entry I look on >> the parent or execute a block if i'm an orphan." >> >> ^ self >> propertyAt: aKey >> ifAbsent: [ >> self hasParent >> ifTrue: [ self parent propertyAt: aKey >> default: aBlock ] >> ifFalse: aBlock ] >> >> but >> >> propertyAt: aKey ifAbsent: aBlock >> "Answer the value of the property ==aKey==, or the result of >> ==aBlock== if the property doesn't exist." >> >> ^ self properties at: aKey ifAbsent: aBlock >> >> propertyAt: aKey ifAbsentPut: aBlock >> "Answer the value of the property ==aKey==, or if the property >> doesn't exist adds and answers the result of evaluating ==aBlock==." >> >> ^ self properties at: aKey ifAbsentPut: aBlock >> >> >> >> In PetitParser there is no lookup. But we can get back to this situation >> by just not setting a parent. >> My gut feeling is telling me that overriding on write is not really good >> because >> a client of the parent will not see the changes coming from a child. >> >> >> I thaought that stylesheet was supporting lookup but it does not >> >> testSubstyleAttributesOverride >> styleSheet at: #textColor put: #red. >> styleSheet > #sub > #subsub at: #textColor put: #blue. >> self assert:( styleSheet get: #textColor ) equals: #red. >> self assert:( styleSheet > #sub get: #textColor ) equals: #red. >> self assert:( styleSheet > #sub > #subsub get: #textColor ) >> equals: #blue. >> Does not work >> >> >> What you think? >> >> Stef >> >> >

March 18, 2017

Re: [Pharo-dev] platforms/Nopsys submodule

by Stephane Ducasse

Hi jan this is super cool. Now with the bootstrap of the system as well as the possibility using guille approach to generate smaller image this open a lot of space. stef On Sat, Mar 18, 2017 at 4:53 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > This is so cool!!! > > 2017-03-18 16:30 GMT+01:00 jan.struz <public+pharo(a)struz.cz>: > >> Hi, >> please stop for a while... I want to show you something... >> >> >> >> Actually it is already done... >> Save The World! >> >> ------------------------------ >> View this message in context: Re: platforms/Nopsys submodule >> <http://forum.world.st/platforms-Nopsys-submodule-tp4939215p4939230.html> >> Sent from the Pharo Smalltalk Developers mailing list archive >> <http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html> at >> Nabble.com. >> > >

March 18, 2017