From: james@peacemax.org (J.D.)
Subject: [TUHS] what is the progress on porting 32V to x86 platform
Date: Tue, 06 Apr 2004 11:41:04 -0600 [thread overview]
Message-ID: <4072EBB0.7090903@peacemax.org> (raw)
To all concerned,
I was wondering what progress has been made in porting 32V to the
x86 platform.
I would like to keep track of it's development. Maybe even dedicate
a web site just for 32V/32I on x86. I'm not certain on how to setup a
repository, but I'm willing to learn as I go.
I have a DSL connection. 3 dedicated IP addresses (1 DNS, 1 mail
server, 1 web server). The web server has 80Gb of storage space and is
running Slackware Linux 9.1. I currently host my own web site:
http://www.peacemax.org on the web server.
I would really like to see a free / low cost UNIX or UNIX-like OS
for the x86 platform come to fruition without the legal battles that
Linux and BSD have had to deal with over the years.
Thank you,
James Falknor
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4766 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20040406/3e095d58/attachment.bin>
next reply other threads:[~2004-04-06 17:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-06 17:41 J.D. [this message]
2004-04-08 0:13 ` Pat Villani
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=4072EBB0.7090903@peacemax.org \
--to=james@peacemax.org \
/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).