From: forsyth@caldo.demon.co.uk forsyth@caldo.demon.co.uk
Subject: [9fans] Plan9 on NeXT
Date: Mon, 12 Jan 1998 18:11:14 -0500 [thread overview]
Message-ID: <19980112231114.DI8ggjQU6ouskeTTgNxx_8YHck1bir1GOPNK5hT69bQ@z> (raw)
>>machine, can i build a 9nextstationcpu for it as well... this binary
probably. compare for instance the configuration files
/sys/src/9/ss/ss and /sys/src/9/ss/sscpu
doing something similar to produce nextstationcpu should
be fairly easy and will probably work.
next reply other threads:[~1998-01-12 23:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-12 23:11 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-01-05 1:51 Brandon
1997-12-24 0:04 Rob
1997-12-23 21:12 Brandon
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=19980112231114.DI8ggjQU6ouskeTTgNxx_8YHck1bir1GOPNK5hT69bQ@z \
--to=forsyth@caldo.demon.co.uk \
/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).