[HECnet] DECnet-Plus on Tru64

[hvlems at zonnet.nl]

Generating your own licenses is indeed a fine ability, wish I could do that for a Pascal license. The hobbyist pak expires every year. 
-----Original Message-----
From: Cory Smelosky <b4 at gewt.net>
Sender: owner-hecnet at Update.UU.SE
Date: Wed, 13 Feb 2013 08:39:22 
To: hecnet at Update.UU.SE<hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SECc: hecnet at Update.UU.SE<hecnet at Update.UU.SE>
Subject: Re: [HECnet] DECnet-Plus on Tru64

On 13 Feb 2013, at 03:48, hvlems at zonnet.nl wrote:

I switch off data mode on my phone owing to the volume on this list and get out of sync with the messageflow. 

What I find interesting is that you seemed able to load the licenses while the entered information was incorrect?

I didn't have actual licenses, so I need to generate valid licenses.   I was able to input a valid but incorrect license. ;)


-----Original Message-----
From: Cory Smelosky <b4 at gewt.net>
Sender: owner-hecnet at Update.UU.SE
Date: Wed, 13 Feb 2013 01:32:35 
To: hecnet at Update.UU.SE<hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SECc: hecnet at Update.UU.SE<hecnet at Update.UU.SE>
Subject: Re: [HECnet] DECnet-Plus on Tru64

On 13 Feb 2013, at 01:30, hvlems at zonnet.nl wrote:

Why don't you run lmf and have a look what it thinks you've done?
Commands are the same as for vms. 
My understanding is that -END gives you endnode functionality. -EXT I cannot remember.

I did that and I then noticed I reversed ISSUER and PRODUCER. ;)

-----Original Message-----
From: Cory Smelosky <b4 at gewt.net>
Sender: owner-hecnet at Update.UU.SE
Date: Wed, 13 Feb 2013 00:04:09 
To: hecnet at Update.UU.SE<hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SECc: hecnet at Update.UU.SE<hecnet at Update.UU.SE>
Subject: Re: [HECnet] DECnet-Plus on Tru64

On 12 Feb 2013, at 23:58, Dave McGuire <mcguire at neurotica.com> wrote:

On 02/12/2013 11:54 PM, Cory Smelosky wrote:
You are not trying to use VMS licenses on Tru64unix, are you?
They aren't compatible, unfortunately. You need real Tru64
licenses.

I am using Tru64 licenses...I just don't know the license names
I need...the documentation seems to not be fond of saying...

Can you run "strings" on the binary and see if you can find out
what it wants?

Ran it on the binaries, the libraries, and finally found the licenses
mentioned in a shell script that is part of the kernel module rebuild
procedure.   I loaded those and NCL still complains...maybe I need to
reinstall the subsets?

This ain't Windows, man.   There's gotta be something else going on.

Maybe I need to recompile the kernel? ;)
I think there is an in-kernel license cache of some sort...perhaps not having the licenses loaded at install affected the way the module was built?

Has to either be that, a trailing space, or incorrect license names.


                -Dave

-- 
Dave McGuire, AK4HZ
New Kensington, PA
.