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

Re: [Pharo-dev] Does OSSubprocess works on ARM vm?

by Eliot Miranda

> On May 15, 2017, at 5:16 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > > 2017-05-15 14:04 GMT+02:00 Mariano Martinez Peck <marianopeck(a)gmail.com>: >> Denis, you can also have shortcut methods to call shell from OSSubprocess. See the tests under "tests - shell" protocol. > > I tried this: > > OSSUnixSubprocess new > shellCommand: 'ls ~'; > redirectStdout; > runAndWaitOnExitDo: [ :process :outString | > ^outString > ]. Try something like shellCommand: 'bash -c ''ls ~'''; > > And it still returns empty string without error in console. With "ls ../" it works fine

May 15, 2017

Re: [Pharo-dev] Does OSSubprocess works on ARM vm?

by Denis Kudriashov

2017-05-15 14:04 GMT+02:00 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Denis, you can also have shortcut methods to call shell from OSSubprocess. > See the tests under "tests - shell" protocol. I tried this: OSSUnixSubprocess new shellCommand: 'ls ~'; redirectStdout; runAndWaitOnExitDo: [ :process :outString | ^outString ]. And it still returns empty string without error in console. With "ls ../" it works fine

May 15, 2017

Re: [Pharo-dev] Does OSSubprocess works on ARM vm?

by Mariano Martinez Peck

Denis, you can also have shortcut methods to call shell from OSSubprocess. See the tests under "tests - shell" protocol. Cheers, On Mon, May 15, 2017 at 8:00 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > 2017-05-15 12:13 GMT+02:00 K K Subbu <kksubbu.ml(a)gmail.com>: > >> ~ is a shell language synonym for $HOME. Both are expanded by the shell >> before calling file syscall in the kernel. Kernel's filename resolver does >> not do ~ or $HOME expansions. >> > > Thanks Subbu :) > -- Mariano http://marianopeck.wordpress.com

May 15, 2017

Re: [Pharo-dev] Does OSSubprocess works on ARM vm?

by Denis Kudriashov

2017-05-15 12:13 GMT+02:00 K K Subbu <kksubbu.ml(a)gmail.com>: > ~ is a shell language synonym for $HOME. Both are expanded by the shell > before calling file syscall in the kernel. Kernel's filename resolver does > not do ~ or $HOME expansions. > Thanks Subbu :)

May 15, 2017

Re: [Pharo-dev] Does OSSubprocess works on ARM vm?

by Denis Kudriashov

2017-05-15 12:10 GMT+02:00 tesonep(a)gmail.com <tesonep(a)gmail.com>: > Hi Denis, > the ~ (tilde) is expanded by the shell, a running process should expand > it. In the case of the command line tools they don't expand it, as they > expect the shell to expand it before calling. > > Check https://www.gnu.org/software/bash/manual/html_ > node/Tilde-Expansion.html > and http://www.davidverhasselt.com/expanding-a-leading-tilde-in-cc/ > Thank's Pablo

May 15, 2017

Re: [Pharo-dev] Use of minimal image

by Pavel Krivanek

2017-05-15 12:05 GMT+02:00 K K Subbu <kksubbu.ml(a)gmail.com>: > Hi, > > I am tempted ;-) by the following message on Pharo's download page: > --- > The minimal image is a reduced version of Pharo 7.0 (alpha): You have the > most basic environment and you can interact with it via command line. > WARNING: For hackers only! > --- > > What kind of hacking has been done with this image in the past ? > > Can this image be used as a swiss-army knife for st (ala busybox in GNU)? > > The image is small enough to ship as part of regular VM binary and > plugins. If pharo (binary) is run without any image, this image can be used > as a fallback to run st scripts. At launch time, we know underlying > platform OS and architecture, so we could move a lot of platform-specific > vm code into such st scripts. > > Or, we could use it within Makefiles to build plugins outside of src tree. > The main purpose of this image was to provide base for reloading of Pharo from packages using Metacello. Now it starts to be obsolete because it was done by top-down shrinking that is replaced by bootstrapping. The image is quite big, it contains Opal, basic network support, Monticello and Metacello. With bootstrap we are able to generate smaller images where this "minimal" image is part of reloading steps. This image should be able to support small custom web server. -- Pavel > > Regards .. Subbu > >

May 15, 2017

Re: [Pharo-dev] Does OSSubprocess works on ARM vm?

by K K Subbu

On Monday 15 May 2017 03:31 PM, Denis Kudriashov wrote: > > It returns empty string and console report: > > ls: cannot access ~: No such file or directory > > Any idea why it not works properly? (from command line "ls ~" returns > expected files). ~ is a shell language synonym for $HOME. Both are expanded by the shell before calling file syscall in the kernel. Kernel's filename resolver does not do ~ or $HOME expansions. Regards .. Subbu

May 15, 2017

Re: [Pharo-dev] Does OSSubprocess works on ARM vm?

by tesonep＠gmail.com

Hi Denis, the ~ (tilde) is expanded by the shell, a running process should expand it. In the case of the command line tools they don't expand it, as they expect the shell to expand it before calling. Check https://www.gnu.org/software/bash/manual/html_node/Tilde-Expansion.html and http://www.davidverhasselt.com/expanding-a-leading-tilde-in-cc/ Cheers, Pablo On Mon, May 15, 2017 at 12:01 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Little problem which I not understand. Maybe you can explain. Path '~' is > not recognizied in ls command: > > OSSUnixSubprocess new > command: '/bin/ls'; > arguments: #('~'); > redirectStdout; > runAndWaitOnExitDo: [ :process :outString | > outString > ] > > > It returns empty string and console report: > > ls: cannot access ~: No such file or directory > > Any idea why it not works properly? (from command line "ls ~" returns > expected files). > > 2017-05-15 11:52 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > >> I just checked. It works perfectly. >> >> One notice for API: >> >> OSSUnixSubprocess new >> command: '/bin/ls'; >> arguments: #('-la' '/Users'); >> redirectStdout; >> runAndWaitOnExitDo: [ :process :outString | >> outString >> ] >> >> Why you are not return result of block? It would be very handy >> (here it is an OSSUnixSubprocess instance). >> >> >> >> 2017-05-12 14:18 GMT+02:00 Mariano Martinez Peck <marianopeck(a)gmail.com>: >> >>> mmmm I don't know. Can you at least try for the first time in a 32 bits >>> ARM ? >>> >>> On Fri, May 12, 2017 at 5:00 AM, Denis Kudriashov <dionisiydk(a)gmail.com> >>> wrote: >>> >>>> Hi. >>>> >>>> I decided to ask before I will try it. >>>> >>>> Best regards, >>>> Denis >>>> >>> >>> >>> >>> -- >>> Mariano >>> http://marianopeck.wordpress.com >>> >> >> > -- Pablo Tesone. tesonep(a)gmail.com

May 15, 2017

Use of minimal image

by K K Subbu

Hi, I am tempted ;-) by the following message on Pharo's download page: --- The minimal image is a reduced version of Pharo 7.0 (alpha): You have the most basic environment and you can interact with it via command line. WARNING: For hackers only! --- What kind of hacking has been done with this image in the past ? Can this image be used as a swiss-army knife for st (ala busybox in GNU)? The image is small enough to ship as part of regular VM binary and plugins. If pharo (binary) is run without any image, this image can be used as a fallback to run st scripts. At launch time, we know underlying platform OS and architecture, so we could move a lot of platform-specific vm code into such st scripts. Or, we could use it within Makefiles to build plugins outside of src tree. Regards .. Subbu

May 15, 2017

Re: [Pharo-dev] Does OSSubprocess works on ARM vm?

by Denis Kudriashov

Little problem which I not understand. Maybe you can explain. Path '~' is not recognizied in ls command: OSSUnixSubprocess new command: '/bin/ls'; arguments: #('~'); redirectStdout; runAndWaitOnExitDo: [ :process :outString | outString ] It returns empty string and console report: ls: cannot access ~: No such file or directory Any idea why it not works properly? (from command line "ls ~" returns expected files). 2017-05-15 11:52 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > I just checked. It works perfectly. > > One notice for API: > > OSSUnixSubprocess new > command: '/bin/ls'; > arguments: #('-la' '/Users'); > redirectStdout; > runAndWaitOnExitDo: [ :process :outString | > outString > ] > > Why you are not return result of block? It would be very handy > (here it is an OSSUnixSubprocess instance). > > > > 2017-05-12 14:18 GMT+02:00 Mariano Martinez Peck <marianopeck(a)gmail.com>: > >> mmmm I don't know. Can you at least try for the first time in a 32 bits >> ARM ? >> >> On Fri, May 12, 2017 at 5:00 AM, Denis Kudriashov <dionisiydk(a)gmail.com> >> wrote: >> >>> Hi. >>> >>> I decided to ask before I will try it. >>> >>> Best regards, >>> Denis >>> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > >

May 15, 2017