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] plan9port update
Date: Sun, 16 Jan 2005 22:23:51 -0800	[thread overview]
Message-ID: <7DD37218104E31429E79EB0BB136800E11C560@vargas.ntdom.cupdx> (raw)

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

Minus the Sparc assembly, will it still run on Sparc?  
 
As for Tru64, to my knowledge, no one has done any Alpha related work in some time...  I'd be interested to see if plan9port runs on Tru64, too...  Unfortunately, my Tru64-system-to-be isn't quite functional.... yet.
 
-Ben
 

	-----Original Message----- 
	From: YAMANASHI Takeshi [mailto:9.nashi@gmail.com] 
	Sent: Sun 1/16/2005 9:10 PM 
	To: 9fans@cse.psu.edu 
	Cc: 
	Subject: Re: [9fans] plan9port update
	
	

	I don't know what I'm writing exactly but...
	
	> There is a big update to Plan 9 port available now, at
	> http://swtch.com/plan9port.
	 :
	> It also means porting the system is easier --
	> there's no sparc assembly at all in the tree, for example.
	
	Does this means I can compile and run p9port on Tru64 UNIX?
	When I tried last, there was no lock related assembly codes there.
	--
	
	
	


[-- 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: 4182 bytes --]

             reply	other threads:[~2005-01-17  6:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-17  6:23 Benjamin Huntsman [this message]
2005-01-20  1:11 ` William K. Josephson
  -- strict thread matches above, loose matches on Subject: below --
2005-01-17  5:10 YAMANASHI Takeshi
2005-01-17 16:01 ` Russ Cox
2005-01-14 21:23 Russ Cox
2005-01-14 23:31 ` David Leimbach
2005-01-17 12:32 ` Matthias Teege
2005-01-17 16:02   ` Russ Cox
2005-01-17 16:15   ` andrey mirtchovski
2005-01-17 16:13     ` boyd, rounin
2005-01-18 18:49   ` Russ Cox
2005-01-18 23:26     ` Noah Evans
2005-01-18  5:56 ` kvchokw02
2005-01-18 18:31   ` Russ Cox
2005-01-18 19:01     ` Ronald G. Minnich
2005-01-19  6:53     ` kvchokw02

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=7DD37218104E31429E79EB0BB136800E11C560@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).