Re: [9fans] Plan9 usage but used to parallel MPI on linux..

[Chris McGee]

I would be interested in manuals or papers on this subject as well.

Plan9 is well suited to distributed computing with its per process namespaces 
and network transparent resource access. Do grid computing projects built on 
plan9 use the built-in OS facilities such as cpu and 9p or do they generally 
favour custom protocols and for what reasons?

Cheers,
Chris

> On Oct 30, 2016, at 8:33 PM, Darren Wise  wrote:
> 
> Heya folks,
> 
> Can anyone point me in the right direction of some manuals concerning the use 
> of a beowulf cluster style of computing setup, i'm so used to MPI installs 
> and limiting myself to terminals that being what it seems ooout-f-he-box this 
> already is setup with parallel computing in mind..
> 
> Also some examples would be great of common current usages of such.
> 
> 
> 
> > Kind regards,
> > Darren Wise Esq, 
> > B.Sc , HND, GNVQ, City & Guilds.
> > 
> > Managing Director (MD)
> > Art Director (AD)
> > Chief Architect/Analyst (CA/A)
> > Chief Technical Officer (CTO)
> > 
> > www.wisecorp.co.uk 
> > www.wisecorp.co.uk/babywise 
> > www.darrenwise.co.uk 

Re: [9fans] Making available a pre-compiled go binary for Miller's plan-9 Pi image (Chris McGee)

[Stanley Lieber]

Chris McGee  wrote:

>I tried this command with both go 1.7.3 and master branches. Both fail
>right after “ Building packages and commands for host, plan9/386”
>with an error “install: ./install not found.”
>
>It seems like the go bootstrap tool is trying to call a binary called
>“install” but there are none on my system. Is there such a command on
>p9bl? Maybe 9front doesn’t have it?
>
>It works fine if I don’t try to cross compile to plan9/arm or even
>linux/386.
>
>Chris
>
>> On Oct 30, 2016, at 4:39 AM, David du Colombier <0in...@gmail.com>
>wrote:
>> 
>> > To cross compile with make.rc do you just set GOARCH and GOOS and
>just run it?
>> 
>> Yes and you can add the --no-rebuild flag to prevent cmd/dist to
>remove the existing binaries.
>> 
>> For example:
>> 
>> ℅ GOOS=plan9 GOARCH=arm make.rc --no-rebuild
>> 
>> -- 
>> David du Colombier
>> 

'install' is from BSD. It does not exist in Plan 9.

sl

[9fans] Plan9 usage but used to parallel MPI on linux..

[Darren Wise]

Heya folks,
Can anyone point me in the right direction of some manuals concerning the use 
of a beowulf cluster style of computing setup, i'm so used to MPI installs and 
limiting myself to terminals that being what it seems ooout-f-he-box this 
already is setup with parallel computing in mind..
Also some examples would be great of common current usages of such.


> Kind regards,
> Darren Wise Esq, 
> B.Sc, HND, GNVQ, City & Guilds.
> 
> Managing Director (MD)
> Art Director (AD)
> Chief Architect/Analyst (CA/A)
> Chief Technical Officer (CTO)
> 
> www.wisecorp.co.uk> www.wisecorp.co.uk/babywise
> www.darrenwise.co.uk

Re: [9fans] Making available a pre-compiled go binary for Miller's plan-9 Pi image (Chris McGee)

[Chris McGee]

I tried this command with both go 1.7.3 and master branches. Both fail right 
after “ Building packages and commands for host, plan9/386” with an error 
“install: ./install not found.”

It seems like the go bootstrap tool is trying to call a binary called “install” 
but there are none on my system. Is there such a command on p9bl? Maybe 9front 
doesn’t have it?

It works fine if I don’t try to cross compile to plan9/arm or even linux/386.

Chris

> On Oct 30, 2016, at 4:39 AM, David du Colombier <0in...@gmail.com> wrote:
> 
> > To cross compile with make.rc do you just set GOARCH and GOOS and just run 
> > it?
> 
> Yes and you can add the --no-rebuild flag to prevent cmd/dist to remove the 
> existing binaries.
> 
> For example:
> 
> ℅ GOOS=plan9 GOARCH=arm make.rc --no-rebuild
> 
> -- 
> David du Colombier
> 

Re: [9fans] acme tag bars stacking

[Mathieu Lonjaret]

yeah, good points.

On 29 October 2016 at 00:47, yy  wrote:
> On 28 October 2016 at 16:23, Mathieu Lonjaret
>  wrote:
>> Anyway, does anyone know what the rationale was for choosing to stack
>> them at the bottom? Or why it would be a a bad idea to make them stack
>> at the top instead?
>
> Let's suppose you have many windows in a column. When you work in one
> of them, you B2 it and put it on the top of the stack. Then you work
> on another one and it goes to the top, moving the previous one to the
> second position, and so on. This way, your most recently used windows
> are always on top, the least used ones go to the bottom of the stack.
> I would find counterintuitive that the windows you used a longer time
> ago stayed at the top, between your "working windows" and the column
> and main tag lines.
>
> But I would guess the main reason it works this way is that it seemed
> more natural to move a window to the head than to the tail of a linked
> list, and it just worked well enough.
>
> I see how it may be more practical to stack them at the top when
> working only with two or three windows, but it would be kind of weird
> if you have ten. If you feel it will fit your workflow better, it is
> probably not too difficult to get it done.
>
>
> --
> - yiyus || JGL .
>

Re: [9fans] Making available a pre-compiled go binary for Miller's plan-9 Pi image (Chris McGee)

[David du Colombier]

> To cross compile with make.rc do you just set GOARCH and GOOS and just
run it?

Yes and you can add the --no-rebuild flag to prevent cmd/dist to remove the
existing binaries.

For example:

℅ GOOS=plan9 GOARCH=arm make.rc --no-rebuild

-- 
David du Colombier