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?
-----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
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
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.
-----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
On 13 Feb 2013, at 00:41, Gregg Levine <gregg.drwho8 at gmail.com> wrote:
On Wed, Feb 13, 2013 at 12:33 AM, Cory Smelosky <b4 at gewt.net> wrote:
On 13 Feb 2013, at 00:14, Cory Smelosky <b4 at gewt.net> wrote:
On 13 Feb 2013, at 00:10, Kari Uusim ki <uusimaki at exdecfinland.org> wrote:
If you have registered and loaded the licenses successfully, but still DECnet-OSI won't start, you might have too few license units for the system type.
Can you tell a bit more about your system and the licenses you are trying to use. THat would be helpful.
On 13.2.2013 6:50, Cory Smelosky wrote:
On 12 Feb 2013, at 23:46, Kari Uusim ki <uusimaki at exdecfinland.org> 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...
Kari
On 13.2.2013 4:56, Cory Smelosky wrote:
Hello!
I'm been playing with Tru64 and I managed to get DECnet
installed...some common library files referred to DECNET-OSI-END and
DECNET-OSI-EXT, are these the correct licenses, or need I load others?
NCL continues to complain despite having those licenses loaded.
Any help appreciated...
.
.
REASON: DECnet License Failure
Description: There is a problem with the DECnet License
Reason = License Not Installed
bash-4.0# /usr/sbin/lmf list
Product Status Users: Total Active
DECNET-OSI-END active unlimited
DECNET-OSI-EXT active unlimited
Both have UNITS set to 0.
The shell script that told me these is as follows:
if lmfck DECNET-OSI-EXT DEC 1.0 8-FEB-1993
then
EXTENDED_LICENSE="yes"
else
if lmfck DECNET-OSI-END DEC 1.0 8-FEB-1993
then
END_SYSTEM_LICENSE="yes"
else
Found the problem. Producer was set to something other than DEC. Oops...
Hello!
I arranged that.
Just like I arranged to have a very large tribble keep Sampsa awake
all night with its noises. And no one wants to know what happened
around Dave's place.
------
Any time any of you want me to stop throwing stuff like all of that
into our list messaging I will. But these discussions are moderately
flat as a <Something else> and sometimes informative, so I figured
some theater would break up the boredom and what mediocrity that seems
to have followed it.
I have no problem with you throwing that stuff in...it often functions as welcome comic relief. ;)
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
On 02/13/2013 12:41 AM, Gregg Levine wrote:
Just like I arranged to have a very large tribble keep Sampsa awake
all night with its noises. And no one wants to know what happened
around Dave's place.
------
Any time any of you want me to stop throwing stuff like all of that
into our list messaging I will. But these discussions are moderately
flat as a <Something else> and sometimes informative, so I figured
some theater would break up the boredom and what mediocrity that seems
to have followed it.
I consider it your trademark. ;) That said, though, personally I find
the conversations here quite stimulating!
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On Wed, Feb 13, 2013 at 12:33 AM, Cory Smelosky <b4 at gewt.net> wrote:
On 13 Feb 2013, at 00:14, Cory Smelosky <b4 at gewt.net> wrote:
On 13 Feb 2013, at 00:10, Kari Uusim ki <uusimaki at exdecfinland.org> wrote:
If you have registered and loaded the licenses successfully, but still DECnet-OSI won't start, you might have too few license units for the system type.
Can you tell a bit more about your system and the licenses you are trying to use. THat would be helpful.
On 13.2.2013 6:50, Cory Smelosky wrote:
On 12 Feb 2013, at 23:46, Kari Uusim ki <uusimaki at exdecfinland.org> 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...
Kari
On 13.2.2013 4:56, Cory Smelosky wrote:
Hello!
I'm been playing with Tru64 and I managed to get DECnet
installed...some common library files referred to DECNET-OSI-END and
DECNET-OSI-EXT, are these the correct licenses, or need I load others?
NCL continues to complain despite having those licenses loaded.
Any help appreciated...
.
.
REASON: DECnet License Failure
Description: There is a problem with the DECnet License
Reason = License Not Installed
bash-4.0# /usr/sbin/lmf list
Product Status Users: Total Active
DECNET-OSI-END active unlimited
DECNET-OSI-EXT active unlimited
Both have UNITS set to 0.
The shell script that told me these is as follows:
if lmfck DECNET-OSI-EXT DEC 1.0 8-FEB-1993
then
EXTENDED_LICENSE="yes"
else
if lmfck DECNET-OSI-END DEC 1.0 8-FEB-1993
then
END_SYSTEM_LICENSE="yes"
else
Found the problem. Producer was set to something other than DEC. Oops...
Hello!
I arranged that.
Just like I arranged to have a very large tribble keep Sampsa awake
all night with its noises. And no one wants to know what happened
around Dave's place.
------
Any time any of you want me to stop throwing stuff like all of that
into our list messaging I will. But these discussions are moderately
flat as a <Something else> and sometimes informative, so I figured
some theater would break up the boredom and what mediocrity that seems
to have followed it.
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
On 13 Feb 2013, at 00:14, Cory Smelosky <b4 at gewt.net> wrote:
On 13 Feb 2013, at 00:10, Kari Uusim ki <uusimaki at exdecfinland.org> wrote:
If you have registered and loaded the licenses successfully, but still DECnet-OSI won't start, you might have too few license units for the system type.
Can you tell a bit more about your system and the licenses you are trying to use. THat would be helpful.
On 13.2.2013 6:50, Cory Smelosky wrote:
On 12 Feb 2013, at 23:46, Kari Uusim ki <uusimaki at exdecfinland.org> 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...
Kari
On 13.2.2013 4:56, Cory Smelosky wrote:
Hello!
I'm been playing with Tru64 and I managed to get DECnet
installed...some common library files referred to DECNET-OSI-END and
DECNET-OSI-EXT, are these the correct licenses, or need I load others?
NCL continues to complain despite having those licenses loaded.
Any help appreciated...
.
.
REASON: DECnet License Failure
Description: There is a problem with the DECnet License
Reason = License Not Installed
bash-4.0# /usr/sbin/lmf list
Product Status Users: Total Active
DECNET-OSI-END active unlimited
DECNET-OSI-EXT active unlimited
Both have UNITS set to 0.
The shell script that told me these is as follows:
if lmfck DECNET-OSI-EXT DEC 1.0 8-FEB-1993
then
EXTENDED_LICENSE="yes"
else
if lmfck DECNET-OSI-END DEC 1.0 8-FEB-1993
then
END_SYSTEM_LICENSE="yes"
else
Found the problem. Producer was set to something other than DEC. Oops...
On 13 Feb 2013, at 00:10, Kari Uusim ki <uusimaki at exdecfinland.org> wrote:
If you have registered and loaded the licenses successfully, but still DECnet-OSI won't start, you might have too few license units for the system type.
Can you tell a bit more about your system and the licenses you are trying to use. THat would be helpful.
On 13.2.2013 6:50, Cory Smelosky wrote:
On 12 Feb 2013, at 23:46, Kari Uusim ki <uusimaki at exdecfinland.org> 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...
Kari
On 13.2.2013 4:56, Cory Smelosky wrote:
Hello!
I'm been playing with Tru64 and I managed to get DECnet
installed...some common library files referred to DECNET-OSI-END and
DECNET-OSI-EXT, are these the correct licenses, or need I load others?
NCL continues to complain despite having those licenses loaded.
Any help appreciated...
.
.
REASON: DECnet License Failure
Description: There is a problem with the DECnet License
Reason = License Not Installed
bash-4.0# /usr/sbin/lmf list
Product Status Users: Total Active
DECNET-OSI-END active unlimited
DECNET-OSI-EXT active unlimited
Both have UNITS set to 0.
The shell script that told me these is as follows:
if lmfck DECNET-OSI-EXT DEC 1.0 8-FEB-1993
then
EXTENDED_LICENSE="yes"
else
if lmfck DECNET-OSI-END DEC 1.0 8-FEB-1993
then
END_SYSTEM_LICENSE="yes"
else
If you have registered and loaded the licenses successfully, but still DECnet-OSI won't start, you might have too few license units for the system type.
Can you tell a bit more about your system and the licenses you are trying to use. THat would be helpful.
On 13.2.2013 6:50, Cory Smelosky wrote:
On 12 Feb 2013, at 23:46, Kari Uusim ki <uusimaki at exdecfinland.org> 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...
Kari
On 13.2.2013 4:56, Cory Smelosky wrote:
Hello!
I'm been playing with Tru64 and I managed to get DECnet
installed...some common library files referred to DECNET-OSI-END and
DECNET-OSI-EXT, are these the correct licenses, or need I load others?
NCL continues to complain despite having those licenses loaded.
Any help appreciated...
.
.
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
