From: wes.parish@paradise.net.nz (Wesley Parish)
Subject: [TUHS] While on the subject of 32V ...
Date: Tue, 21 Oct 2003 13:50:55 +1300 [thread overview]
Message-ID: <200310211350.55658.wes.parish@paradise.net.nz> (raw)
In-Reply-To: <3F93E4AC.9050403@hp.com>
I tried the same with a few of the utilities and a make with the kernel files.
<shock and awe>Dependencies again</shock and awe> - with most of the utilities
the compile was easy, since their dependencies were easily filled by the
standard Linux C libraries. Since many of the kernel dependencies depend on
the vax specific .s files and I don't know anything about the vax at the
moment, I decided to leave it until I _did_ know. That's why I've been
asking stoopid questions on this list.
Well, if you're keen on it, I am too. I need something to do over the
holidays.
Wesley Parish
On Tue, 21 Oct 2003 02:35, Pat Villani wrote:
> Folks,
>
> I recently copied down the 32V source, and compiled the kernel with gcc.
> Much to my surprise, most of it compiled. I then split out the machine
> dependent versus the machine independent files (loose classification :-),
> and compiled again. Naturally, in both cases, you could not actually build
> a kernel because there are vax specific .s files, but the individual C
> files compiled. Not a bad start.
>
> As a result, I've been giving serious consideration to porting it to Intel
> IA32 platforms. It'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. The Caldera
> license is pretty much a BSD license, which could be considered an open
> source license. This means I should be able to work on it without worrying
> about IP, although I'd still need management approval.
>
> Should I undertake such an project, would there be enough interest to
> justify the effort?
>
> Pat
--
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."
next prev parent reply other threads:[~2003-10-21 0:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-20 13:35 Pat Villani
2003-10-21 0:50 ` Wesley Parish [this message]
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
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
[not found] <20031021020017.5B7961F4F@minnie.tuhs.org>
2003-10-21 3:51 ` [TUHS] While on the subject of 32V Phil Garcia
2003-10-21 19:45 Steve Nickolas
2003-10-30 12:57 David Presotto
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=200310211350.55658.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).