> Yeah, thank goodness for snapshots :O Running replica/pull didn't turn out
> so good for my current running system. It looks like it might make the most
> sense to just archive my home directory and reload a fresh VM ...
>
> Where are they keeping the most current installation ISO these days?
> Where are they keeping the most current installation ISO these days? I'm
> just not sure of what's canonical now that the old bell-labs.com domain is
> offline.
David is in charge of legacy Plan 9 outside of Bell Labs. His instructions were
pretty explicit, but if you run into trouble I'll be
Hi all,
I've been getting interested in programming in Go recently and it's my
understanding that at some point in time, Plan 9 was a supported
environment in which one could bootstrap and use Go?
I've tried a few different versions; 1.2.2, 1.4.2, 1.5.2, just following
the directions that I
>From http://fqa.9front.org/appendixl.html:
# automatically converted ca certs from mozilla.org
hget http://curl.haxx.se/ca/cacert.pem >/sys/lib/tls/ca.pem
# shell script that emulates git commands
hget http://9front.org/extra/rc/git >$home/bin/rc/git
chmod
Go builds just fine right now on the plan9 builders: http://build.golang.org
1.4 and 1.5 are very different, due to 1.5 being written in Go. i386 and amd64
should both build, although amd64 fails an irrelevant unittest.
What do you see with 1.5.2/1.5.3? (You said you tried?)
Best regards,
All the errors seem related to the old Rune size. I suspect you're running
an old system and it's likely to not have nsec and tsemacquire syscalls
either.
If you believe the system is up-to-date, you can cross compile a simple Go
program using 1.5 or later targeting GOOS=plan9 GOARCH=386 from a
Thanks, Skip. That would follow; this system is probably straight Fourth
Edition, certainly an old ISO...
I've never been 100% clear on the process for running updates; can I bring
myself up to current from where I'm at now and not have to reload or build
a fresh system? It's a VM and I can
> All the errors seem related to the old Rune size. I suspect you're running
> an old system and it's likely to not have nsec and tsemacquire syscalls
> either.
>
> If you believe the system is up-to-date, you can cross compile a simple Go
> program using 1.5 or later targeting GOOS=plan9
> Go builds just fine right now on the plan9 builders: http://build.golang.org
>
> 1.4 and 1.5 are very different, due to 1.5 being written in Go. i386 and
> amd64 should both build, although amd64 fails an irrelevant unittest.
>
> What do you see with 1.5.2/1.5.3? (You said you tried?)
Note:
> I'm looking at the directions in a (cached copy) of
> http://plan9.bell-labs.com/wiki/plan9/Staying_up_to_date/index.html...
>
> Is that still valid? What's the canonical procedure these days for updating
> a system?
>
> If that's roughly correct ... I'm running a single Plan 9 machine, combined
> Note: I'm running 9front. I can build on amd64 but not 386. Last attempt
> was 1.5 on 386, bootstrapped with 1.4.2:
>
> dl; go version
> go version go1.4.2 plan9/386
> dl; GOROOT_BOOTSTRAP=/usr/local/go
> dl; ./make.rc
> # Building Go bootstrap tool.
>
> % 9fs sources
> % 9fat:
> % cp /n/sources/plan9/386/9pcf /n/9fat
> % cp /n/sources/plan9/386/9pccpu /n/9fat
> % hget http://www.9legacy.org/download/kernel/9pccpuf >/n/9fat
Of course, I mean:
hget http://www.9legacy.org/download/kernel/9pccpuf >/n/9fat/9pccpuf
--
David du Colombier
Also the ports tree[1] version of golang should install fine. I haven't
tried it in a while, but also haven't changed it so it should work. That
will grab the ca certs and install (I think) 1.3.
--
Veety
Answering my own silly question, on my fossil-based system, running the
following command on the console as the bootes user seems to get the update
process running:
replica/pull -v /dist/replica/network
I'll wait for this to complete and then give building Go another shot.
Thanks for answering
Sean,
David's (0intro) instructions are the right way to do it. If I recall
correctly, if you want to update by rebuilding from updated sources,
there's a careful dance that needs to happen for the transition from old
Rune size to the new. Geoff sent out a note to 9fans outlining the steps
at
Yeah, thank goodness for snapshots :O Running replica/pull didn't turn out
so good for my current running system. It looks like it might make the most
sense to just archive my home directory and reload a fresh VM ...
Where are they keeping the most current installation ISO these days? I'm
just
16 matches
Mail list logo