Thanks David.
> How did you succeed to run go_bootstrap? Have you
> just switched from the 9atom pc kernel to the pcpae
> kernel?
I just switched from 9atom pc to pcpae kernel.
When I run /usr/sys/src/go/src/all.rc, it fails
to make $GOROOT/include/plan9/libc_plan9.h.
Then, I removed the lines o
> before the Go 1.4 release.
Sorry, I mean Go 1.3 of course.
--
David du Colombier
Two days ago, I've fixed the script mklibc.rc to
generate the libc_plan9.h file properly on 9atom.
https://codereview.appspot.com/82660044/
Please give a try and review this change to
get it submitted before the Go 1.4 release.
--
David du Colombier
> Someone can explain the meaning of the last error?
> --- FAIL: TestResolveIPAddr (0.00 seconds)
> ipraw_test.go:74: ResolveIPAddr(ip6:ipv6-icmp, ::1) failed: write
> /net/cs: cs: no match
> FAIL
> FAIL net 0.948s
The ResolveIPAddr test is failing because you don't have
the ::1 addre
I built pcpae kernel and recompiled go distribution,
and probably success.
Attached is the go compilation result, and the last line
shows the used go version.
Someone can explain the meaning of the last error?
Kenji
# Building C bootstrap tool.
cmd/dist
# Building compilers and Go bootstrap tool
Hi,
As I cannot force plan 9 to use my sata disk, I've decided to buy a sata to usb
convertor.
After compiling the usb tools on 9atom, I can find my disk under /dev/sdU1.0
and now is the time to
prepare the disk partitions in order to install plan 9. Disk which I want to
use isn't empty
(it con
> I've attached image of the result of the command. I hope that soon I will be
> able to
> attach it in plain text format :). I'm afraid that my Ethernet card is not
> recognised too.
> Can you recommend any PCI Ethernet card that is known to be working under
> Plan 9?
anything intel gigabit+p
wrt this
> On Apr 1, 2014, at 8:15 AM, erik quanstrom wrote:
>
> oh, the atom usb stick can be installed on a mac pro.
> just dd the image to a hard drive, and proceed as normal.
> make sure not to overwrite the install image while installing.
> there's no safety check for that. word of caution:
i was wondering if anyone had any ideas on this.
the hda manual isn't that easy to read. :-)
i have a mac pro with an audiohda chipset that works,
but the gain is 0. this is because aout has no out amp
(0x11 & 4)==0.
i'm not sure if the issue is that we need to
walk the widget chain until we fi
On Tue Apr 1 04:47:27 EDT 2014, adriano.vera...@mail.com wrote:
> Testing an rc script under Bell and Atom I noted that Atom dd doesn't
> implement the "oseekb" option.
>
> bs=1 allows to seek at any given byte offset but, what is the impact on
> speedness ?
>
> And, in any case, isn't it a (IM
> Ok, I'll try it.
> I have somewhat complicated feeling on linux's PAE kernal.
> Isn't ther anything wrong to run pae kernel, somthing
> like some application don't run on it etc.
everything should run fine.
- erik
Testing an rc script under Bell and Atom I noted that Atom dd doesn't
implement the "oseekb" option.
bs=1 allows to seek at any given byte offset but, what is the impact on
speedness ?
And, in any case, isn't it a (IMHO small) portability problem ?
adriano
Hi there everyone,
Many thanks for the explanation, it's much clearer now.
2014-04-01 9:24 GMT+02:00 Mark van Atten :
> On Mon, Mar 31, 2014 at 5:54 PM, Daniel Peyrolon
> wrote:
> >> Edit , x/^[^ ]+[ ]*[^(]*\([^)]*\)[ ]*\{[ ]*\n/ s/[ ]*\{[ ]*\n/\n\{/g
> >
> > So, it was simply a matter of chan
On Mon, Mar 31, 2014 at 5:54 PM, Daniel Peyrolon wrote:
>> Edit , x/^[^ ]+[ ]*[^(]*\([^)]*\)[ ]*\{[ ]*\n/ s/[ ]*\{[ ]*\n/\n\{/g
>
> So, it was simply a matter of changing "$" for "\n" at the x command!
Yes. (In the version I gave, the replacement of the second $, the one
in the s command, by \n w
14 matches
Mail list logo
