9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] spin models
Date: Thu,  2 Dec 2004 00:31:33 +0000	[thread overview]
Message-ID: <219622be950eb9f8dd35d935a8ca91d1@vitanuova.com> (raw)
In-Reply-To: <200412011102.iB1B2rd14890@zamenhof.cs.utwente.nl>

> not that I'm much of a spin expert (we have one/some here,
> don't know if he/they will be available during twente9con), but
> running xspin (4.2.0) in simulation and/or verification mode
> on slave2.spin brings me further than rog suggested in his mail.

i tried it on what i believe to be to the latest version (4.2.1),
and the main problem (fixed limit on number of channels created)
still seems to be there.

i don't think it was envisaged that channels might be used in this
way.



      reply	other threads:[~2004-12-02  0:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-16 18:55 [9fans] interaction of lnfs and autocompletion Skip Tavakkolian
2004-11-16 19:35 ` rog
2004-11-16 20:04   ` [9fans] spin models rog
2004-11-17  0:07     ` Charles Forsyth
2004-12-01 11:02       ` Axel Belinfante
2004-12-02  0:31         ` rog [this message]

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=219622be950eb9f8dd35d935a8ca91d1@vitanuova.com \
    --to=rog@vitanuova.com \
    --cc=9fans@cse.psu.edu \
    /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).