From: Wes Kussmaul <wes@ReliableID.com>
To: 9fans@9fans.net
Subject: Re: [9fans] rc exec error behaviour
Date: Tue, 2 Feb 2016 12:33:21 -0500 [thread overview]
Message-ID: <56B0E861.9090801@ReliableID.com> (raw)
In-Reply-To: <CAJSxfm+6OxwEujFRmhC8503fC2ivBwpp48Opuw740iyBQWQ7iA@mail.gmail.com>
Now's your chance!
No match for domain "9COULD.NET". >>> Last update of whois database:
Tue, 02 Feb 2016 17:22:15 GMT <<<
On 02/02/2016 11:52 AM, Skip Tavakkolian wrote:
> Autocorrect fail! And yet Apple is winning big. Sigh...
>
> I mean 9pcloud.net <http://9pcloud.net>
>
> On Tue, Feb 2, 2016 at 8:46 AM Skip Tavakkolian
> <skip.tavakkolian@gmail.com <mailto:skip.tavakkolian@gmail.com>> wrote:
>
> Same here. The namespace manager for 9pcould.net
> <http://9pcould.net> is written in Go and most definitely runs on
> a (slightly modified) Labs Plan 9, 386.
>
> On Tue, Feb 2, 2016 at 7:47 AM <lucio@proxima.alt.za
> <mailto:lucio@proxima.alt.za>> wrote:
>
> > 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).
>
> Are you all saying that Go does not work on Plan 9 legacy and
> that all
> my code is just faking it?
>
> I know Go is broken in my 9vx installation, but that could be
> really
> hard to fix. Took a while last time and would have taken
> much, much
> longer without help from Anthony Martin.
>
> Lucio.
>
>
--
Wes Kussmaul
The Authenticity Institute
738 Main Street
Waltham, MA 02451
office +1 781 790 1674
mobile +1 781 330 1881
THIS COMMUNICATION IS INTENDED ONLY FOR THE USE OF THE PERSON TO WHOM IT IS ADDRESSED. If it was addressed incorrectly there's not much I can do but ask you politely to pretend you didn't see it. Any disclaimer suggesting that the sender has some kind of recourse is just wishful thinking.
If I had a message from you that was digitally signed using your Sigillum™ identity credential from the Osmio Vital Records Department (http://osmio.ch), we could easily and at no cost exchange encrypted messages and files with each other.
next prev parent reply other threads:[~2016-02-02 17:33 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
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 [this message]
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=56B0E861.9090801@ReliableID.com \
--to=wes@reliableid.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).