[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Lynx-dev] Version Inqury

From: Johnson, Tracy
Subject: RE: [Lynx-dev] Version Inqury
Date: Tue, 15 Feb 2011 09:30:58 -0500

Well, since HP doesn't know who wrote the port (I presume they have read
any readme file or source in it's subdirectory) I'm going to guess that
HP will not be able to send me a copy.

I've been getting explicit permissions from various authors who wrote
various code on the MPE platform.  The lynx port is just one of them.

To explain here is the effective situation:

1) The platform in question was the INVENT3K machine that HP had on the
Internet for a number of years.  

2) HP has donated that platform's license to OpenMPE, Inc.  (I sit on
the OpenMPE board, this is my task.)

3) HP included everything on that machine except for code and ports
written by private individuals and outside parties.  

4) OpenMPE has in turn, put that platform back on the Internet.

5) HP will cut me a tape (file) from the original machine for the code
that I got permissions.  The last person at HP who has access do that
machine will be powering that machine down, effectively turning off the
lights at the end of the month.

6) I've been tracking down permissions from these individuals and
parties.  I'm in the process of forwarding those to my contact at HP.

7) Then I can put the code back on the INVENT3K machine.

So far I've gotten permissions from most of the known parties.
Obviously, code marked as "author unknown" (such as lynx) has been
harder to track.  This is what led me here.

The worst case is OpenMPE will never get the code.  Since OpenMPE will
be making the machine available again, someone could write a new port,
if desired.

Tracy Johnson
Office 1-757-766-4318

> -----Original Message-----
> From: Thomas Dickey [mailto:address@hidden 
> Sent: Tuesday, February 15, 2011 5:22 AM
> To: Johnson, Tracy
> Cc: address@hidden
> Subject: RE: [Lynx-dev] Version Inqury
> On Mon, 14 Feb 2011, Johnson, Tracy wrote:
> >> On Mon, 14 Feb 2011, Johnson, Tracy wrote:
> >>
> >>> Hello I just subscribed.
> >>>
> >>> I'm trying to discover who wrote the lynx port to the MPE 
> operating
> >>> system.
> >>>
> >>> Any ideas?
> >>>
> >>> HP has it on one remaining server and lists it as 'author 
> unknown'.
> >>
> >> I haven't seen that.  googling, I can see some mention of it
> >> (  That would be before I started working on
> >> it in 1997.
> >> At that point, there was a top-level makefile with ~40 targets to
> >> customize for various platforms.
> >>
> >> None of those mentioned MPE (though there may have been other
> >> names for
> >> it).  For instance, there's some "snake" target which I never
> >> was able to
> >> identify.  Even for that, there's no author mentioned.
> >>
> >> Where's the package?
> >>
> >> --
> >> Thomas E. Dickey
> >>
> >>
> >
> > The source is on one server that is off the grid at HP.
> >
> > HP is willing to cut a copy for me if I can get 
> 'permission' from the
> > author.
> >
> > Robelle was not on my radar however.
> Robelle's webpage refers to the website at University of 
> Kansas (which 
> could refer to any time before 1997).  While it's possible 
> that the MPE 
> port was done prior to the 2.4 release in 1995 (which seems to be the 
> first using the GPL), it's unlikely.
> The earliest version that I have at hand (2.4.2, November 
> 1996) uses the 
> same "COPYHEADER" file which exists (updated) in current 
> code. That gives 
> a 1995 date for copyright by University of Kansas, states 
> that the code is 
> released using GPL version 2, and that inquiries should be 
> directed to 
> Michael Grobe.
> That file, and the text for the GPL (in "COPYING") are supposed to be 
> included in any package.  They provide "'permission' from the author".
> So all you need to do is to point this out to HP...
> > Fortunately I'm one of their customers.  I can ask them if they had
> > anything to do with it.
> They might or might not.  The HP porting center has a 
> mixture, with often 
> incorrect summaries, and I've pointed out corrections to it more than 
> once.
> -- 
> Thomas E. Dickey

reply via email to

[Prev in Thread] Current Thread [Next in Thread]