The following executables are installed into $GOROOT/bin as Plan 9
a.out binaries when you run make -k install inside src/pkg:
cgo, ebnflint, gofix, gofmt, gotest, gotype, govet, goyacc, hgpatch.
They should be directed somewhere else by setting GOBIN, there is no
need to include them in your
The following executables are installed into $GOROOT/bin as Plan 9
a.out binaries when you run make -k install inside src/pkg:
cgo, ebnflint, gofix, gofmt, gotest, gotype, govet, goyacc, hgpatch.
They should be directed somewhere else by setting GOBIN, there is no
need to include them in your
Ok. I have installed Plan9 in an empty hard disk and the bootloader works fine.
have the bootloader got any problems if the Plan9 partition is above
1024 cylinders?
Cheers.
pmarin
On Sat, Apr 9, 2011 at 7:18 AM, pmarin pmarin.m...@gmail.com wrote:
I have a problem after installing 9atom in an
On Sun Apr 10 09:12:49 EDT 2011, pmarin.m...@gmail.com wrote:
Ok. I have installed Plan9 in an empty hard disk and the bootloader works
fine.
have the bootloader got any problems if the Plan9 partition is above
1024 cylinders?
i'm glad you got things working.
clearly the pbs loaded
the problem with commit messsages has been
fixed by steve. stallion/mercurial
thanks for the bug reports.
- erik
Ruby is my language of choice. It was natural to use it for Plan 9
application development which involves working with dictiories, stacks
and some metaprogramming.
I took fgb/ruby, localized changes, wrote mkfile
https://gist.github.com/912507 And it was ok until I've started
GUI part. It appears
Hi, it's me, the repeating person (I almost said broken record but
I'm not sure how many people know what that means any more :-)
Suggest you run your command with ratrace
ratrace - whatevercommandyouarerunning
It can be very revealing.
ron
Sergey Kish sergey.k...@gmail.com once said:
Today I've implemented same on go. It also falls but it may be my
fault
error: read /dev/draw/new: unknown id for draw image
You're giving bad data to devdraw. The Go code on the gist
is sending
long(id) 'n' long(id) byte(namelen)
Another thing to check would be any encoding of the data
passed to a write, i.e., try opening the data file in
binary mode.
Anthony
