The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: wes.parish@paradise.net.nz (Wesley Parish)
Subject: 32V update (was Re: [TUHS] While on the subject of 32V ...)
Date: Fri, 31 Oct 2003 23:13:03 +1300	[thread overview]
Message-ID: <200310312313.03329.wes.parish@paradise.net.nz> (raw)
In-Reply-To: <3FA10A89.7090901@hp.com>

It's downloaded.

I would suggest renaming it to something like 32V-x86, though - makes it 
easier to remember it's not going to be precisely the same as 32V for VAX.

In relation to corporate caveats, the only way you could actually compete with 
HP is if somehow, in a matter of months, you redid the entire development of 
BSD and SVRx, up to the stage HP-UX currently is at.

Oh well, time for me to brush off my Pajari book on Unix device drivers and 
see if I can make the grade! ;)

Wesley Parish


On Fri, 31 Oct 2003 01:56, Pat Villani wrote:
> I got corporate approval, well, as best as I could from corporate legal,
> to proceed.  The only caveats are: beware of the SCO shenanigans as 32V
> may encounter a similar wrath, and make sure I don't "compete" with HP.
>   How in the world a 15 year old operating system threatens SCO or
> competes with HP is beyond me.  At any rate, I'll start moving the email
> activity off the corporate network soon, in order to comply with open
> source participation rules.
>
> In the meantime, I have just placed a copy of the reorganized kernel
> files in ftp://server.opensourcedepot.com/pub/32V. This is my personal
> server, so it's easy for me to put source code there, at least for now.
>   The reorganization consists mainly of separating out drivers, and a
> scratch file for a locore.asm file.  I also placed formalized license
> notices in the directory and files, so to alert everyone of the license
> terms.
>
> It's a start ...
>
> Pat
>
>
>
>
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> http://minnie.tuhs.org/mailman/listinfo/tuhs

-- 
Clinesterton Beademung - in all of love.
Mau e ki, "He aha te mea nui?"
You ask, "What is the most important thing?"
Maku e ki, "He tangata, he tangata, he tangata."
I reply, "It is people, it is people, it is people."


  reply	other threads:[~2003-10-31 10:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-20 13:35 [TUHS] While on the subject of 32V Pat Villani
2003-10-21  0:50 ` Wesley Parish
2003-10-21 14:00   ` Pat Villani
2003-10-22  8:10     ` Wesley Parish
2003-10-24 13:41       ` Pat Villani
2003-10-29  9:01         ` Wesley Parish
2003-10-30 12:56         ` 32V update (was Re: [TUHS] While on the subject of 32V ...) Pat Villani
2003-10-31 10:13           ` Wesley Parish [this message]
2003-10-31 14:26             ` Pat Villani
2003-11-05  2:22           ` Greg Lehey
2003-11-05 12:53             ` Pat Villani
     [not found] ` <200311022346.34747.wes.parish@paradise.net.nz>
     [not found]   ` <oprx0h6gtdrveh1e@smtp.borf.com>
2003-11-03 10:48     ` Wesley Parish
2003-11-03 15:34       ` Pat Villani
2003-11-04  9:56         ` Wesley Parish
2003-11-04 13:51           ` Pat Villani
2003-10-31 22:37 Robertdkeys
2003-10-31 23:53 ` Gregg C Levine
2003-11-04 18:18 macbiesz
2003-11-05 10:23 ` Wesley Parish

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=200310312313.03329.wes.parish@paradise.net.nz \
    --to=wes.parish@paradise.net.nz \
    /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).