From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: [9fans] plan9ports to NetBSD
Date: Tue, 7 Dec 2004 11:03:02 +0200 [thread overview]
Message-ID: <038021ee700f4c13187b3e750f329d99@proxima.alt.za> (raw)
I can get most of the way there, but
<sched.h>
and
sched_yield()
concern me. The former seems quite unrelated to the 9ports altogether
and the latter does not appear in NetBSD (1.6.1, nearly up to date) at
all.
Also, there are no (ffork rendez)^-NetBSD.c routines and in my
ignorance I'm not sure which of Free- and Open-BSD is better suited (I
think the "rendez-" are identical, mind you).
For the record, I downloaded plan9-20040708.tar.gz which seems close
to being the final word, if the web site is to be believed.
All help welcome, I miss mk greatly.
++L
next reply other threads:[~2004-12-07 9:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-07 9:03 Lucio De Re [this message]
2004-12-07 18:22 ` William Josephson
2004-12-07 18:37 ` Micah Stetson
2004-12-08 3:55 ` Lucio De Re
2004-12-07 17:09 Richard C Bilson
2004-12-07 17:27 ` Lucio De Re
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=038021ee700f4c13187b3e750f329d99@proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).