[TUHS] While on the subject of 32V ...

[Wesley Parish]

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."