From: "Mathieu L." <lejatorn@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] 9vx as a perfect proto environment
Date: Wed, 30 Sep 2009 22:47:09 +0200 [thread overview]
Message-ID: <e44157893b27c4527d4c16e12a5c0488@smgl.fr.eu.org> (raw)
In-Reply-To: <Pine.BSI.4.64.0909260844540.23231@malasada.lava.net>
[-- Attachment #1: Type: text/plain, Size: 188 bytes --]
Indeed, I've just retried with the latest pull from hg and that problem
is gone for me, that's brilliant.
That's one less thing to worry about with 9vx, cheers for that. ☺
Mathieu
[-- Attachment #2: Type: message/rfc822, Size: 4244 bytes --]
From: Tim Newsham <newsham@lava.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9vx as a perfect proto environment
Date: Sat, 26 Sep 2009 08:45:48 -1000 (HST)
Message-ID: <Pine.BSI.4.64.0909260844540.23231@malasada.lava.net>
> I'm using 9vx as my primary development platform, and even though it's
> fantastic to have a Plan 9 environment so easily setup and integrated
> to the host OS, it has its limits. For example it will crash if your
> badly written program tries to read on a hanged up connection, or it
> will freeze if you run a buggy program in acid with truss.
is this with the latest 9vx or the bin snapshot? I know the
snapshot didnt ignore SIGPIPE which would cause the whole vm to
shutdown when writing to a socket that shut down. However, that
should be fixed in the latest sources.
> Mathieu
Tim Newsham
http://www.thenewsh.com/~newsham/
next prev parent reply other threads:[~2009-09-30 20:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-26 0:40 ron minnich
2009-09-26 0:47 ` Lyndon Nerenberg - VE6BBM/VE7TFX
2009-09-30 14:23 ` Ethan Grammatikidis
2009-09-30 18:45 ` erik quanstrom
2009-10-01 0:19 ` Ethan Grammatikidis
2009-10-01 3:53 ` lucio
2009-09-26 11:31 ` Richard Miller
2009-09-26 14:52 ` blstuart
2009-09-26 15:29 ` Mathieu L.
2009-09-26 18:45 ` Tim Newsham
2009-09-30 20:47 ` Mathieu L. [this message]
2009-09-27 17:14 ` Russ Cox
2009-09-27 17:52 ` blstuart
2009-09-28 12:01 ` Iruata Souza
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=e44157893b27c4527d4c16e12a5c0488@smgl.fr.eu.org \
--to=lejatorn@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).