9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Benjamin Huntsman" <BHuntsman@mail2.cu-portland.edu>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: RE: [9fans] archmp
Date: Tue, 23 Nov 2004 21:55:29 -0800	[thread overview]
Message-ID: <7DD37218104E31429E79EB0BB136800E11C4E7@vargas.ntdom.cupdx> (raw)

[-- Attachment #1: Type: text/plain, Size: 532 bytes --]

by the way, do many use Plan 9 on MP systems, or is it just there in-case?

	-----Original Message----- 
	From: jmk@plan9.bell-labs.com [mailto:jmk@plan9.bell-labs.com] 
	Sent: Tue 11/23/2004 9:45 PM 
	To: 9fans@cse.psu.edu 
	Cc: 
	Subject: Re: [9fans] archmp
	
	

	Of course, the other place a specific architecture has to
	deal with MP issues is the MMU. It's possible to make that
	really complicated, but Plan 9 skirts most of that at the
	expense of some performance and generality in odd cases.
	
	--jim
	


[-- Attachment #2.1: Type: text/plain, Size: 292 bytes --]

from postmaster@ethel:
The following attachment had content that we can't
prove to be harmless.  To avoid possible automatic
execution, we changed the content headers.
The original header was:

	Content-Type: application/ms-tnef;
	name="winmail.dat"
	Content-Transfer-Encoding: base64

[-- Attachment #2.2: winmail.dat.suspect --]
[-- Type: application/octet-stream, Size: 3590 bytes --]

             reply	other threads:[~2004-11-24  5:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-24  5:55 Benjamin Huntsman [this message]
2004-11-24  7:05 ` geoff
2004-11-24  9:25 ` Christopher Nielsen
  -- strict thread matches above, loose matches on Subject: below --
2004-11-24  5:54 Benjamin Huntsman
2004-11-24 16:02 ` jmk
2004-11-24  5:45 jmk
2004-11-24  4:44 Benjamin Huntsman
2004-11-24  4:55 ` Russ Cox
2004-11-24  5:18 ` jmk

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=7DD37218104E31429E79EB0BB136800E11C4E7@vargas.ntdom.cupdx \
    --to=bhuntsman@mail2.cu-portland.edu \
    --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).