From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] plan9ports to NetBSD
Date: Wed, 8 Dec 2004 05:55:33 +0200 [thread overview]
Message-ID: <a3e9aaeae7bc7203742373a0636e8a24@proxima.alt.za> (raw)
In-Reply-To: <20041207182242.GB21003@mero.morphisms.net>
> What do you mean by ``unrelated''? As I recall it is there so that
> the lock routines can yield the processor. I expect that sleep() is
> sufficient, but it is there for a reason.
Oh, I meant that the NetBSD header file didn't have anything in it
that resembled the use p9ports made of it. Just my ignorance, I have
to admit. Of course, NetBSD and multiprocessing are still in their
infancy.
As you suggest, NetBSD 2 may well be a more interesting target.
++L
next prev parent reply other threads:[~2004-12-08 3:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-07 9:03 Lucio De Re
2004-12-07 18:22 ` William Josephson
2004-12-07 18:37 ` Micah Stetson
2004-12-08 3:55 ` Lucio De Re [this message]
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=a3e9aaeae7bc7203742373a0636e8a24@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).