From: "Mathieu L." <lejatorn@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] 9vx as a perfect proto environment
Date: Sat, 26 Sep 2009 17:29:35 +0200 [thread overview]
Message-ID: <106cd7072d11102d3e0badff68c25d62@smgl.fr.eu.org> (raw)
In-Reply-To: <46da41288d9f1b334030ffde38b09d9b@bellsouth.net>
[-- Attachment #1: Type: text/plain, Size: 495 bytes --]
I've definitely seen it on linux.
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.
Still, it's so convenient compared to dual booting or qemu that I prefer
sticking with it.
Cheers,
Mathieu
[-- Attachment #2: Type: message/rfc822, Size: 4004 bytes --]
From: blstuart@bellsouth.net
To: 9fans@9fans.net
Subject: Re: [9fans] 9vx as a perfect proto environment
Date: Sat, 26 Sep 2009 09:52:23 -0500
Message-ID: <46da41288d9f1b334030ffde38b09d9b@bellsouth.net>
> I've had less success using it for "real work", at least on MacOS
> 10.5 and 10.6 - for example running a venti server eventually
> results in something like
> 9vx panic: sigsegv on cpu7
I've seen similar on FreeBSD, though I don't think I've see it
on Linux. I use 9vx pretty much all the time as my terminal
and stand-alone when I'm not connected to my network. In
those uses, a crash once or twice a day hasn't been bad enough
to make me investigate.
BLS
next prev parent reply other threads:[~2009-09-26 15:29 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. [this message]
2009-09-26 18:45 ` Tim Newsham
2009-09-30 20:47 ` Mathieu L.
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=106cd7072d11102d3e0badff68c25d62@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).