[Info-vax] FreeAXP/Avanti 2.2.0.435 Released

[VAXman- at SendSpamHere.ORG]

In article <k5nh9g$qkj$1 at dont-email.me>, Stephen Hoffman <seaohveh at hoffmanlabs.invalid> writes:
>On 2012-10-17 23:16:03 +0000, David Froble said:
>
>> JF Mezei wrote:
>>> On 12-10-17 17:10, VAXman- @SendSpamHere.ORG wrote:
>>> 
>>>> I've ported 100s of VAX applications, utilities, drivers, etc. to Alpha.
>>>> I've never found anything difficult or impossible, and I never found a 
>>>> single bit of VAX software that was not portable.
>>> 
>>> Try porting VAX applications that made use of Message Router callable
>>> interface.  Since the later was not ported to Alpha, it becomes prety
>>> hard to port your apps to Alpha.
>
>Not the first prerequisite that's gone missing.  Undoubtedly not the 
>last, either.
>
>> What is so hard about writing your own messaging software.
>
>Well, beyond designing and writing and maintaining it, getting past my 
>own dislike of writing stuff that somebody else has probably already 
>written?
>
>It might pay to look at ZeroMQ, or another package, for instance.
>
>> Might be more usable to your particular software than some generic package.
>
>For me, it's more a case of what's central to the value-add I'm aiming 
>for, and what's not.  If there is some reason {performance, features, 
>whatever} to create a custom implementation, have at.  But for other 
>cases, rolling your own implementation ties up your own staff writing 
>and supporting something that doesn't move your primary {product, 
>service, whatever} forward.  That's bad.
>
>> Can you give me examples of procedures than can be done on a VAX that 
>> cannot be done on an Alpha, or IA-64?
>
>Accessing Q-bus and Unibus widgets would be somewhat gnarly.

If you can get me an Alpha or an Integrity with a Q-bus or Unibus and the
device controller(s) in question, I'll do it. ;)

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

Well I speak to machines with the voice of humanity.