From: David du Colombier <0intro@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] rc exec error behaviour
Date: Tue, 2 Feb 2016 14:23:50 +0100 [thread overview]
Message-ID: <CANUoZoEo1VDp8r2gx=569e48uL_TFCaBvHRhmi2zX-4oa3cA0g@mail.gmail.com> (raw)
In-Reply-To: <CAEAzY3-GuDUAKbd3FxXtO5q6xBnvAGAVif-dnbffa_bjYE1qzw@mail.gmail.com>
> For 386, Go barely works. For amd64, current Go doesn't currently work
> on 9front (but works on Charles' kernel), probably due to a kernel
> bug.
You got confused. It works (but there are still issues) on both 9front's
and Charles' amd64 kernel, but not on 9front's 386 kernel (since November 2014).
> Btw, Go broke on 9front about a year ago (or was it more than that?).
> Only one single person noticed, and that was months later after the
> fact. That serves as a useful test to gauge interest (and quality) in
> Go on Plan 9.
Another reason could be that most of 9front users use the
amd64 kernel and not the 386 kernel.
--
David du Colombier
next prev parent reply other threads:[~2016-02-02 13:23 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-30 16:31 cinap_lenrek
2016-01-31 1:16 ` Prof Brucee
2016-01-31 4:20 ` lucio
2016-01-31 6:58 ` Skip Tavakkolian
2016-02-01 0:52 ` Sean Hinchee
2016-02-01 4:06 ` erik quanstrom
2016-02-01 4:29 ` lucio
2016-02-01 17:01 ` Richard Miller
2016-02-01 18:35 ` lucio
2016-02-02 1:29 ` Prof Brucee
2016-02-02 10:53 ` Richard Miller
2016-02-02 12:36 ` Aram Hăvărneanu
2016-02-02 12:53 ` hiro
2016-02-02 13:23 ` David du Colombier [this message]
2016-02-02 15:46 ` lucio
2016-02-02 16:02 ` David du Colombier
2016-02-02 16:46 ` Skip Tavakkolian
2016-02-02 16:52 ` Skip Tavakkolian
2016-02-02 17:11 ` sl
2016-02-03 0:37 ` Sean Hinchee
2016-02-03 0:48 ` Kurt H Maier
2016-02-02 17:24 ` sl
2016-02-02 17:33 ` Wes Kussmaul
2016-02-01 20:33 ` [9fans] plan9/arm in Go 1.7? (was: rc exec error behaviour) Skip Tavakkolian
2016-02-01 20:45 ` David du Colombier
2016-02-02 4:16 ` [9fans] rc exec error behaviour Lyndon Nerenberg
2016-02-02 4:21 ` Prof Brucee
2016-02-02 4:24 ` Lyndon Nerenberg
2016-02-22 0:19 ` erik quanstrom
2016-02-03 0:48 sl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANUoZoEo1VDp8r2gx=569e48uL_TFCaBvHRhmi2zX-4oa3cA0g@mail.gmail.com' \
--to=0intro@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).