HP3000-L Archives

November 2001, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"VANCE,JEFF (HP-Cupertino,ex1)" <[log in to unmask]>
Reply To:
VANCE,JEFF (HP-Cupertino,ex1)
Date:
Fri, 16 Nov 2001 03:20:29 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (60 lines)
> From: [log in to unmask] [mailto:[log in to unmask]]
> As things stand right now, HP has NO plans to release the
> source code of MPE.

This is actually true. We have no specific plans on open
source vs. limited licensing, vs. keep it all closed, vs.
spin off CSY vs. ???

> They want this OS to go away and stay gone.  Believe
> me, I have my contacts and I will not reveal them nor myself
> for numerous reasons.

Who is "they"?  CSY does not want this OS to go away. We
realize that regardless of our plans and implementation, there
will be customers choosing to use MPE beyond 2006.  These are
sane customers and they will be making a reasonable choice.
At least now they will know HP's role (or lack of) when they
make their decisions.

> If I could make a suggestion, it would be that all of you die
> hard MPE fans contact HP and plead for the source code after the
> support life ends.

Your voices need to be heard loud and clear much sooner than
that, and fortunately they are.

> I hope HP will do the right thing and release the source
> code, maybe that will happen when the company has a new CEO.

A new CEO makes no difference on our open source decision(s).
I think it would be a worthwhile exercise for all those who
favor open MPE source to honestly evaluate how that would
directly benefit you.  I see some benefits and some big risks,
but I'd like to read your views.  Are you going to write a new
driver for MPE when the existing ones are obsolete.  Are you
going to create cPCI for MPE?  Are you going to port MPE to
IA-64?  Are you going to port the MPE compiler to the new
EPIC back-ends?  Are you going to define a new MPE run time
model for IA-64.  Are you going to define a flat 64 bit process
address space?  Are you going to certify new peripherals?  Are
you going to teach our debugger all about the new run time model,
the ELF-2 program structure, flat 64 bit address space, new linker
stuff, etc?  Are you going to write new diagnostics for the new
drivers you write?  Are you going to bring up the next PA processor
and certify it. Are you going to pay someone else to do all or
some of the above?

Are you just going to read source code to learn what a certain data
structure looks like? Do you have the time, money, expertise to deal
with an open MPE?

I know you are feeling that open MPE is better than closed MPE,
but think about it, those are not the only choices.

regards,
 Jeff Vance

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2