9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Iruata Souza <iru.muzgo@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] plan9port openbsd 4.4
Date: Mon, 26 Jan 2009 16:28:57 -0200	[thread overview]
Message-ID: <d1c554290901261028n7cf0410cp20cb0c9857b6d67b@mail.gmail.com> (raw)
In-Reply-To: <dd6fe68a0901260804o44a68863xd9791c411cc4418d@mail.gmail.com>

can't remember on 4.4, but 4.3 did run acme fine.

On Mon, Jan 26, 2009 at 2:04 PM, Russ Cox <rsc@swtch.com> wrote:
> The plan9port code depends on the operating system's pthreads
> being real kernel-level threads, not a fake user-level simulation.
> The user-level simulations are not good enough, because
> on the x86 they cut corners and use the stack pointer
> to locate the thread-local state.  The Plan 9 threaded
> programs manage their own stacks, making it impossible
> for the user-space simulations to find their thread-local state.
>
> Most Linux distributions switched to real threads (i.e., dropped
> LinuxThreads in favor of NPTL) around the time they switched
> to the 2.6 kernel.  FreeBSD switched in the FreeBSD 5 release.
>
> Last I had heard, OpenBSD was still plodding along with
> user-level threads.  Until they fix that, programs like acme
> will not run.
>
> Russ
>
>



--
iru



  parent reply	other threads:[~2009-01-26 18:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-26  1:34 Fernan Bolando
2009-01-26  1:41 ` Iruata Souza
2009-01-26  2:36   ` Fernan Bolando
2009-01-26  2:42 ` andrey mirtchovski
2009-01-26  5:13 ` sqweek
2009-01-26 16:04 ` Russ Cox
2009-01-26 18:01   ` Anthony Sorace
2009-01-29 14:43     ` Mechiel Lukkien
2009-01-26 18:28   ` Iruata Souza [this message]
2009-01-26 21:13     ` Fernan Bolando
2009-01-29 14:31       ` Fernan Bolando

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=d1c554290901261028n7cf0410cp20cb0c9857b6d67b@mail.gmail.com \
    --to=iru.muzgo@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).