From: usagi.tsukino@pinku.zzn.com (Steve Nickolas)
Subject: [TUHS] While on the subject of 32V ...
Date: Tue, 21 Oct 2003 11:45:45 -0800 [thread overview]
Message-ID: <28065AD6560527342A34399F144E81CB@usagi.tsukino.pinku.zzn.com> (raw)
>From: Pat Villani <Pat.Villani at hp.com>
>Sent: Mon, 20 Oct 2003 09:35:40 -0400
>To: tuhs at tuhs.org
>Subject: [TUHS] While on the subject of 32V ...
>Folks,
>I recently copied down the 32V source, and compiled the kernel with
>gcc. \x01Much to my surprise, most of it compiled. \x01I then split out the
>machine dependent versus the machine independent files (loose
>classification :-), and compiled again. \x01Naturally, in both cases, you
>could not actually build a kernel because there are vax specific .s
>files, but the individual C files compiled. \x01Not a bad start.
Whew. Goes to show something about GCC backward compatibility.
>As a result, I've been giving serious consideration to porting it to
>Intel IA32 platforms. \x01It's much simpler than the unix I worked on
>until last year (Tru64, aka OSF/1 and Digital UNIX), and the 32V
>kernel is only a little bigger than the original FreeDOS kernel I
>wrote. \x01The Caldera license is pretty much a BSD license, which could
>be considered an open source license. \x01This means I should be able to
>work on it without worrying about IP, although I'd still need
>management approval.
It's basically the old (with advertising) BSD license, AFAICT.
>Should I undertake such an project, would there be enough interest to
>justify the effort?
I for one would be interested... :)
>Pat
-uso.
next reply other threads:[~2003-10-21 19:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 19:45 Steve Nickolas [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-30 12:57 David Presotto
[not found] <20031021020017.5B7961F4F@minnie.tuhs.org>
2003-10-21 3:51 ` Phil Garcia
2003-10-20 13:35 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
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=28065AD6560527342A34399F144E81CB@usagi.tsukino.pinku.zzn.com \
--to=usagi.tsukino@pinku.zzn.com \
/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).