-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Johnny Billquist
Sent: Monday, November 18, 2013 19:51
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Node data update
On 2013-11-18 21:17, Sampsa Laine wrote:
On 18 Nov 2013, at 00:16, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-11-18 01:13, Johnny Billquist wrote:
On 2013-11-17 23:43, Steve Davidson wrote:
Go for it!
In the end though, I would like to see a distribution
list so that
others may take advantage of this.
No problemo. I have a distribution list on MIM for it now.
MIM::US:[BQT]NOTIFY.DIS
Mail uses LEGATO:: as a gateway, so it will not work if
LEGATO is down.
I should clarify that it means mail to destination outside
of HECnet uses LEGATO. Mail to recipients inside HECnet
requires that those specific machines are online (obviously).
Would the CHIMPY::smtp%"foo at bar.com" format work? I use
that for some distribution lists on say HILANT..
Sure. Any address works equally well, actually. As long as
it's a form of address I can use from MIM. It's just that
LEGATO was in my head as a gateway I had used in the past
which worked for delivering mail to the internet.
Then have both LEGATO and CHIMPY as relays, I doubt we'd be
sending out THAT much mail that getting two copies would
bother the recipient too badly..
Up to whomever wants to to tell me what address they want me
to send to.
Of course, I will eventually move to my own SMTP client on
MIM (once I've written it).
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
The whole point of this exercise was to allow the individual systems to
update (in an automated fashion) their node database when Johnny
publishes an update. The automation requires that only one such notice
per event be sent (from Johnny's proedure) directly to the HECnet
system. That is a system with a DECnet node name/address like SGC::.
In this case the only account that has the priv is SGC::SYSTEM. My
system(s) will run DELIVER and just deal with this operation behind the
scenes. I will not have to step in at any time so I can just forget
about it. DELIVER will parse it, and direct it, such that a process
will kick off that will execute NetUpdateV2.COM. Initially it will be
only SGC:: (SYSTEM). I will add others directly because I will give the
address to Johnny, or I will have SGC:: (SYSTEM) forward it to the other
systems within my network, or some of both. The RSX and RSTS systems
will actually execute IND files. I have not yet figured out how the
ULTRIX systems will handle it. Let's get VMS systems to work first -
then deal with the others.
-Steve
-Steve
On 2013-11-18 21:17, Sampsa Laine wrote:
On 18 Nov 2013, at 00:16, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-11-18 01:13, Johnny Billquist wrote:
On 2013-11-17 23:43, Steve Davidson wrote:
Go for it!
In the end though, I would like to see a distribution list so that
others may take advantage of this.
No problemo. I have a distribution list on MIM for it now.
MIM::US:[BQT]NOTIFY.DIS
Mail uses LEGATO:: as a gateway, so it will not work if LEGATO is down.
I should clarify that it means mail to destination outside of HECnet uses LEGATO. Mail to recipients inside HECnet requires that those specific machines are online (obviously).
Would the CHIMPY::smtp%"foo at bar.com" format work? I use that for some distribution lists on say HILANT..
Sure. Any address works equally well, actually. As long as it's a form of address I can use from MIM. It's just that LEGATO was in my head as a gateway I had used in the past which worked for delivering mail to the internet.
Then have both LEGATO and CHIMPY as relays, I doubt we'd be sending out THAT much mail that getting two copies would bother the recipient too badly..
Up to whomever wants to to tell me what address they want me to send to.
Of course, I will eventually move to my own SMTP client on MIM (once I've written it).
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Sampsa,
I am trying to automate the update of the network database on my systems. One email is all I want to see per update request.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE on behalf of Sampsa Laine
Sent: Mon 11/18/2013 15:17
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Node data update
On 18 Nov 2013, at 00:16, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-11-18 01:13, Johnny Billquist wrote:
On 2013-11-17 23:43, Steve Davidson wrote:
Go for it!
In the end though, I would like to see a distribution list so that
others may take advantage of this.
No problemo. I have a distribution list on MIM for it now.
MIM::US:[BQT]NOTIFY.DIS
Mail uses LEGATO:: as a gateway, so it will not work if LEGATO is down.
I should clarify that it means mail to destination outside of HECnet uses LEGATO. Mail to recipients inside HECnet requires that those specific machines are online (obviously).
Would the CHIMPY::smtp%"foo at bar.com" format work? I use that for some distribution lists on say HILANT..
Then have both LEGATO and CHIMPY as relays, I doubt we'd be sending out THAT much mail that getting two copies would bother the recipient too badly..
Sampsa
On 18 Nov 2013, at 00:16, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-11-18 01:13, Johnny Billquist wrote:
On 2013-11-17 23:43, Steve Davidson wrote:
Go for it!
In the end though, I would like to see a distribution list so that
others may take advantage of this.
No problemo. I have a distribution list on MIM for it now.
MIM::US:[BQT]NOTIFY.DIS
Mail uses LEGATO:: as a gateway, so it will not work if LEGATO is down.
I should clarify that it means mail to destination outside of HECnet uses LEGATO. Mail to recipients inside HECnet requires that those specific machines are online (obviously).
Would the CHIMPY::smtp%"foo at bar.com" format work? I use that for some distribution lists on say HILANT..
Then have both LEGATO and CHIMPY as relays, I doubt we'd be sending out THAT much mail that getting two copies would bother the recipient too badly..
Sampsa
Thank you!
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Johnny Billquist
Sent: Sunday, November 17, 2013 19:24
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Node data update
On 2013-11-18 01:16, Johnny Billquist wrote:
On 2013-11-18 01:13, Johnny Billquist wrote:
On 2013-11-17 23:43, Steve Davidson wrote:
Go for it!
In the end though, I would like to see a distribution
list so that
others may take advantage of this.
No problemo. I have a distribution list on MIM for it now.
MIM::US:[BQT]NOTIFY.DIS
Now moved to US:[DECNET]NOTIFY.DIS, just in case someone
curious wants to look at it. And the execution of things are
done from US:[DECNET]MAKEFILE.
Any further questions can be directed directly to me, and
I'll refrain from spamming this list anymore. :-)
Johnny
Mail uses LEGATO:: as a gateway, so it will not work if
LEGATO is down.
I should clarify that it means mail to destination outside
of HECnet
uses LEGATO. Mail to recipients inside HECnet requires that those
specific machines are online (obviously).
Johnny
Also, sometimes database updates might actually not cause any real
change to the number to name mapping, just as a small warning.
Also, at this time, any additions or removals from that
distribution
are handled be me manually. So let me know if you want to be in or
out of that list.
Johnny
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE on behalf of Johnny Billquist
Sent: Sun 11/17/2013 13:51
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Node data update
On 2013-11-17 19:21, Johnny Billquist wrote:
On 2013-11-17 17:55, Steve Davidson wrote:
Johnny,
How much effort would be involved for your procedures to send
email to a distribution list announcing a change to the network
database? I could hook that at my end to the running of
NetUpdateV2.COM which already makes use of the file
NODENAMES.DAT,
that the current procedure produces. The subject would
have to be
unique so that the parser could deal with it. A mail
message that
looked something like this:
To: @netupdate.dis
Subject: NETUPDATE
Content would be ignored. To subscribe all anyone
would have to do
would be to submit a HECnet email address to you. I
will volunteer
one
right now to test with - SGC::SYSTEM.
Hmm.. Eventually that would be easy, but the one snag
right now is that
I still do not have a resolver library for RSX finished.
Once I've done
this, I can do any such automation quite easily.
It might be that I could set it up using a DECnet-SMTP
gateway right
now. I just need to check this out a little. Let me come
back to you in
a day or so. Right now I'm trying to understand how
network booting
PDP-11s work...
Johnny
Aw, heck. I get distracted easily...
So, to make things clear - you'd like to get a mail with
a specific
subject line? I figured out how to do that. The sender
will be me, and
the to-line would be you... I can set that up now, if you
want to test
it.
Johnny
Regards,
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Johnny
Billquist
Sent: Friday, November 15, 2013 14:22
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Node data update
On 2013-11-15 15:49, Cory Smelosky wrote:
Hey Johnny,
Update the extended data for MOYA please. She is a
MicroVAX II
(KA630) with 13M RAM in a BA123.
Updated the CPU, thanks. Care to tell what OS?
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On 2013-11-18 01:16, Johnny Billquist wrote:
On 2013-11-18 01:13, Johnny Billquist wrote:
On 2013-11-17 23:43, Steve Davidson wrote:
Go for it!
In the end though, I would like to see a distribution list so that
others may take advantage of this.
No problemo. I have a distribution list on MIM for it now.
MIM::US:[BQT]NOTIFY.DIS
Now moved to US:[DECNET]NOTIFY.DIS, just in case someone curious wants to look at it. And the execution of things are done from US:[DECNET]MAKEFILE.
Any further questions can be directed directly to me, and I'll refrain from spamming this list anymore. :-)
Johnny
Mail uses LEGATO:: as a gateway, so it will not work if LEGATO is down.
I should clarify that it means mail to destination outside of HECnet
uses LEGATO. Mail to recipients inside HECnet requires that those
specific machines are online (obviously).
Johnny
Also, sometimes database updates might actually not cause any real
change to the number to name mapping, just as a small warning.
Also, at this time, any additions or removals from that distribution are
handled be me manually. So let me know if you want to be in or out of
that list.
Johnny
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE on behalf of Johnny Billquist
Sent: Sun 11/17/2013 13:51
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Node data update
On 2013-11-17 19:21, Johnny Billquist wrote:
On 2013-11-17 17:55, Steve Davidson wrote:
Johnny,
How much effort would be involved for your procedures to send email
to a
distribution list announcing a change to the network database? I
could
hook that at my end to the running of NetUpdateV2.COM which already
makes use of the file NODENAMES.DAT, that the current procedure
produces. The subject would have to be unique so that the parser
could
deal with it. A mail message that looked something like this:
To: @netupdate.dis
Subject: NETUPDATE
Content would be ignored. To subscribe all anyone would have to do
would be to submit a HECnet email address to you. I will volunteer
one
right now to test with - SGC::SYSTEM.
Hmm.. Eventually that would be easy, but the one snag right now is that
I still do not have a resolver library for RSX finished. Once I've done
this, I can do any such automation quite easily.
It might be that I could set it up using a DECnet-SMTP gateway right
now. I just need to check this out a little. Let me come back to you in
a day or so. Right now I'm trying to understand how network booting
PDP-11s work...
Johnny
Aw, heck. I get distracted easily...
So, to make things clear - you'd like to get a mail with a specific
subject line? I figured out how to do that. The sender will be me, and
the to-line would be you... I can set that up now, if you want to test
it.
Johnny
Regards,
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Johnny Billquist
Sent: Friday, November 15, 2013 14:22
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Node data update
On 2013-11-15 15:49, Cory Smelosky wrote:
Hey Johnny,
Update the extended data for MOYA please. She is a MicroVAX II
(KA630) with 13M RAM in a BA123.
Updated the CPU, thanks. Care to tell what OS?
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On 2013-11-18 01:13, Johnny Billquist wrote:
On 2013-11-17 23:43, Steve Davidson wrote:
Go for it!
In the end though, I would like to see a distribution list so that
others may take advantage of this.
No problemo. I have a distribution list on MIM for it now.
MIM::US:[BQT]NOTIFY.DIS
Mail uses LEGATO:: as a gateway, so it will not work if LEGATO is down.
I should clarify that it means mail to destination outside of HECnet uses LEGATO. Mail to recipients inside HECnet requires that those specific machines are online (obviously).
Johnny
Also, sometimes database updates might actually not cause any real
change to the number to name mapping, just as a small warning.
Also, at this time, any additions or removals from that distribution are
handled be me manually. So let me know if you want to be in or out of
that list.
Johnny
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE on behalf of Johnny Billquist
Sent: Sun 11/17/2013 13:51
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Node data update
On 2013-11-17 19:21, Johnny Billquist wrote:
On 2013-11-17 17:55, Steve Davidson wrote:
Johnny,
How much effort would be involved for your procedures to send email
to a
distribution list announcing a change to the network database? I could
hook that at my end to the running of NetUpdateV2.COM which already
makes use of the file NODENAMES.DAT, that the current procedure
produces. The subject would have to be unique so that the parser could
deal with it. A mail message that looked something like this:
To: @netupdate.dis
Subject: NETUPDATE
Content would be ignored. To subscribe all anyone would have to do
would be to submit a HECnet email address to you. I will volunteer one
right now to test with - SGC::SYSTEM.
Hmm.. Eventually that would be easy, but the one snag right now is that
I still do not have a resolver library for RSX finished. Once I've done
this, I can do any such automation quite easily.
It might be that I could set it up using a DECnet-SMTP gateway right
now. I just need to check this out a little. Let me come back to you in
a day or so. Right now I'm trying to understand how network booting
PDP-11s work...
Johnny
Aw, heck. I get distracted easily...
So, to make things clear - you'd like to get a mail with a specific
subject line? I figured out how to do that. The sender will be me, and
the to-line would be you... I can set that up now, if you want to test
it.
Johnny
Regards,
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Johnny Billquist
Sent: Friday, November 15, 2013 14:22
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Node data update
On 2013-11-15 15:49, Cory Smelosky wrote:
Hey Johnny,
Update the extended data for MOYA please. She is a MicroVAX II
(KA630) with 13M RAM in a BA123.
Updated the CPU, thanks. Care to tell what OS?
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On 2013-11-17 23:43, Steve Davidson wrote:
Go for it!
In the end though, I would like to see a distribution list so that others may take advantage of this.
No problemo. I have a distribution list on MIM for it now. MIM::US:[BQT]NOTIFY.DIS
Mail uses LEGATO:: as a gateway, so it will not work if LEGATO is down. Also, sometimes database updates might actually not cause any real change to the number to name mapping, just as a small warning.
Also, at this time, any additions or removals from that distribution are handled be me manually. So let me know if you want to be in or out of that list.
Johnny
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE on behalf of Johnny Billquist
Sent: Sun 11/17/2013 13:51
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Node data update
On 2013-11-17 19:21, Johnny Billquist wrote:
On 2013-11-17 17:55, Steve Davidson wrote:
Johnny,
How much effort would be involved for your procedures to send email to a
distribution list announcing a change to the network database? I could
hook that at my end to the running of NetUpdateV2.COM which already
makes use of the file NODENAMES.DAT, that the current procedure
produces. The subject would have to be unique so that the parser could
deal with it. A mail message that looked something like this:
To: @netupdate.dis
Subject: NETUPDATE
Content would be ignored. To subscribe all anyone would have to do
would be to submit a HECnet email address to you. I will volunteer one
right now to test with - SGC::SYSTEM.
Hmm.. Eventually that would be easy, but the one snag right now is that
I still do not have a resolver library for RSX finished. Once I've done
this, I can do any such automation quite easily.
It might be that I could set it up using a DECnet-SMTP gateway right
now. I just need to check this out a little. Let me come back to you in
a day or so. Right now I'm trying to understand how network booting
PDP-11s work...
Johnny
Aw, heck. I get distracted easily...
So, to make things clear - you'd like to get a mail with a specific
subject line? I figured out how to do that. The sender will be me, and
the to-line would be you... I can set that up now, if you want to test it.
Johnny
Regards,
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Johnny Billquist
Sent: Friday, November 15, 2013 14:22
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Node data update
On 2013-11-15 15:49, Cory Smelosky wrote:
Hey Johnny,
Update the extended data for MOYA please. She is a MicroVAX II
(KA630) with 13M RAM in a BA123.
Updated the CPU, thanks. Care to tell what OS?
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Go for it!
In the end though, I would like to see a distribution list so that others may take advantage of this.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE on behalf of Johnny Billquist
Sent: Sun 11/17/2013 13:51
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Node data update
On 2013-11-17 19:21, Johnny Billquist wrote:
On 2013-11-17 17:55, Steve Davidson wrote:
Johnny,
How much effort would be involved for your procedures to send email to a
distribution list announcing a change to the network database? I could
hook that at my end to the running of NetUpdateV2.COM which already
makes use of the file NODENAMES.DAT, that the current procedure
produces. The subject would have to be unique so that the parser could
deal with it. A mail message that looked something like this:
To: @netupdate.dis
Subject: NETUPDATE
Content would be ignored. To subscribe all anyone would have to do
would be to submit a HECnet email address to you. I will volunteer one
right now to test with - SGC::SYSTEM.
Hmm.. Eventually that would be easy, but the one snag right now is that
I still do not have a resolver library for RSX finished. Once I've done
this, I can do any such automation quite easily.
It might be that I could set it up using a DECnet-SMTP gateway right
now. I just need to check this out a little. Let me come back to you in
a day or so. Right now I'm trying to understand how network booting
PDP-11s work...
Johnny
Aw, heck. I get distracted easily...
So, to make things clear - you'd like to get a mail with a specific
subject line? I figured out how to do that. The sender will be me, and
the to-line would be you... I can set that up now, if you want to test it.
Johnny
Regards,
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Johnny Billquist
Sent: Friday, November 15, 2013 14:22
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Node data update
On 2013-11-15 15:49, Cory Smelosky wrote:
Hey Johnny,
Update the extended data for MOYA please. She is a MicroVAX II
(KA630) with 13M RAM in a BA123.
Updated the CPU, thanks. Care to tell what OS?
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On 2013-11-17 19:21, Johnny Billquist wrote:
On 2013-11-17 17:55, Steve Davidson wrote:
Johnny,
How much effort would be involved for your procedures to send email to a
distribution list announcing a change to the network database? I could
hook that at my end to the running of NetUpdateV2.COM which already
makes use of the file NODENAMES.DAT, that the current procedure
produces. The subject would have to be unique so that the parser could
deal with it. A mail message that looked something like this:
To: @netupdate.dis
Subject: NETUPDATE
Content would be ignored. To subscribe all anyone would have to do
would be to submit a HECnet email address to you. I will volunteer one
right now to test with - SGC::SYSTEM.
Hmm.. Eventually that would be easy, but the one snag right now is that
I still do not have a resolver library for RSX finished. Once I've done
this, I can do any such automation quite easily.
It might be that I could set it up using a DECnet-SMTP gateway right
now. I just need to check this out a little. Let me come back to you in
a day or so. Right now I'm trying to understand how network booting
PDP-11s work...
Johnny
Aw, heck. I get distracted easily...
So, to make things clear - you'd like to get a mail with a specific subject line? I figured out how to do that. The sender will be me, and the to-line would be you... I can set that up now, if you want to test it.
Johnny
Regards,
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Johnny Billquist
Sent: Friday, November 15, 2013 14:22
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Node data update
On 2013-11-15 15:49, Cory Smelosky wrote:
Hey Johnny,
Update the extended data for MOYA please. She is a MicroVAX II
(KA630) with 13M RAM in a BA123.
Updated the CPU, thanks. Care to tell what OS?
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On 2013-11-17 17:55, Steve Davidson wrote:
Johnny,
How much effort would be involved for your procedures to send email to a
distribution list announcing a change to the network database? I could
hook that at my end to the running of NetUpdateV2.COM which already
makes use of the file NODENAMES.DAT, that the current procedure
produces. The subject would have to be unique so that the parser could
deal with it. A mail message that looked something like this:
To: @netupdate.dis
Subject: NETUPDATE
Content would be ignored. To subscribe all anyone would have to do
would be to submit a HECnet email address to you. I will volunteer one
right now to test with - SGC::SYSTEM.
Hmm.. Eventually that would be easy, but the one snag right now is that I still do not have a resolver library for RSX finished. Once I've done this, I can do any such automation quite easily.
It might be that I could set it up using a DECnet-SMTP gateway right now. I just need to check this out a little. Let me come back to you in a day or so. Right now I'm trying to understand how network booting PDP-11s work...
Johnny
Regards,
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Johnny Billquist
Sent: Friday, November 15, 2013 14:22
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Node data update
On 2013-11-15 15:49, Cory Smelosky wrote:
Hey Johnny,
Update the extended data for MOYA please. She is a MicroVAX II
(KA630) with 13M RAM in a BA123.
Updated the CPU, thanks. Care to tell what OS?
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Johnny,
How much effort would be involved for your procedures to send email to a
distribution list announcing a change to the network database? I could
hook that at my end to the running of NetUpdateV2.COM which already
makes use of the file NODENAMES.DAT, that the current procedure
produces. The subject would have to be unique so that the parser could
deal with it. A mail message that looked something like this:
To: @netupdate.dis
Subject: NETUPDATE
Content would be ignored. To subscribe all anyone would have to do
would be to submit a HECnet email address to you. I will volunteer one
right now to test with - SGC::SYSTEM.
Regards,
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Johnny Billquist
Sent: Friday, November 15, 2013 14:22
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Node data update
On 2013-11-15 15:49, Cory Smelosky wrote:
Hey Johnny,
Update the extended data for MOYA please. She is a MicroVAX II
(KA630) with 13M RAM in a BA123.
Updated the CPU, thanks. Care to tell what OS?
Johnny
On Fri, 15 Nov 2013, Johnny Billquist wrote:
On 2013-11-15 15:49, Cory Smelosky wrote:
Hey Johnny,
Update the extended data for MOYA please. She is a MicroVAX II (KA630)
with 13M RAM in a BA123.
Updated the CPU, thanks. Care to tell what OS?
OpenVMS 7.3 booted from MOIRA.
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Afternoon all,
I can't find manuals for the KA41-A based 3100s, so I am flying completely blind.
When I power on the unit, it behing self tests. It never seems to stop self testing. It stays on 0001 1011 for the LEDs and the console repeatedly reports its doing self-tests. I can't find anything that would tell it to not leave the permanent self-test mode. I have removed the communications option for testing purposes but I highly doubt that's related to what's causing this.
Is there some obvious switch I am missing that tells this to exit self-test mode?
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On 2013-11-15 15:49, Cory Smelosky wrote:
Hey Johnny,
Update the extended data for MOYA please. She is a MicroVAX II (KA630)
with 13M RAM in a BA123.
Updated the CPU, thanks. Care to tell what OS?
Johnny
Sent from mobile device that advertises itself for no good reason
On 15 Nov 2013, at 10:20, "Paul_Koning at Dell.com" <Paul_Koning at Dell.com> wrote:
On Nov 15, 2013, at 8:21 AM, Kari Uusim ki <uusimaki at exdecfinland.org> wrote:
If you connect the MicroVAX ethernet port to a Cisco switch port, check that the Cisco switch port has spanning tree _disabled_
MOP booting and other low level protocols don't cope well with the spanning tree listening period the switch will enforce when the link is reset.
That's hard to believe.
Yeah. Swapping cards out fixed it anyway. MOYA is now semi functional.
Certainly MOP should deal just fine, unless someone implemented it very badly. Ditto any other DEC protocol. After all, DEC invented the spanning tree algorithm, so handling its implications was just elementary network algorithm design for all of us.
paul
Well, I have recent experience of the problem. That's why I mentioned it.
We did do a LAN reconfiguration at the office. We added a dozen Cisco catalyst switches to get rid of the cable spaghetti we had between racks.
After the reconfiguration I was going to boot some of our Alphas and VAXen - which were now connected to the Catalyst switches - from the Infoserver. Earlier there was no problems at all, but now the boot didn't work at all. As there were no other changes made, I suspected the Catalysts. When monitoring what happened during the boot I found out that when the Ethernet adapter resets the link, the Catalyst starts the spanning tree listening period and blocks all traffic to and from the port until the listening period has ended. Unfortunately that seems to be too long a time for the protocol and the boot never continues.
This was verified on other Catalysts as well.
The solution is to disable spanning tree on the port where a booting node is connected. Then the booting problem is gone.
I think it is an overkill from Cisco to implement spanning tree on every possible switch port. I can understand the point, though, because there are too many LAN users nowadays which don't have a clue of what is happening in the LAN.
Regards,
Kari
On 15.11.2013 17:20, Paul_Koning at Dell.com wrote:
On Nov 15, 2013, at 8:21 AM, Kari Uusim ki <uusimaki at exdecfinland.org> wrote:
If you connect the MicroVAX ethernet port to a Cisco switch port, check that the Cisco switch port has spanning tree _disabled_
MOP booting and other low level protocols don't cope well with the spanning tree listening period the switch will enforce when the link is reset.
That's hard to believe.
Certainly MOP should deal just fine, unless someone implemented it very badly. Ditto any other DEC protocol. After all, DEC invented the spanning tree algorithm, so handling its implications was just elementary network algorithm design for all of us.
paul
.
On Nov 15, 2013, at 8:21 AM, Kari Uusim ki <uusimaki at exdecfinland.org> wrote:
If you connect the MicroVAX ethernet port to a Cisco switch port, check that the Cisco switch port has spanning tree _disabled_
MOP booting and other low level protocols don't cope well with the spanning tree listening period the switch will enforce when the link is reset.
That's hard to believe.
Certainly MOP should deal just fine, unless someone implemented it very badly. Ditto any other DEC protocol. After all, DEC invented the spanning tree algorithm, so handling its implications was just elementary network algorithm design for all of us.
paul
Hey Johnny,
Update the extended data for MOYA please. She is a MicroVAX II (KA630)
with 13M RAM in a BA123.
Thanks!
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
If you connect the MicroVAX ethernet port to a Cisco switch port, check that the Cisco switch port has spanning tree _disabled_
MOP booting and other low level protocols don't cope well with the spanning tree listening period the switch will enforce when the link is reset.
Regards,
Kari
On 15.11.2013 15:15, Cory Smelosky wrote:
Sent from mobile device that advertises itself for no good reason
On 15 Nov 2013, at 06:14, "Kari Uusim ki" <uusimaki at exdecfinland.org> wrote:
Hi Cory,
You don't happen to use a Cisco switch when you connect the MicroVAX to your LAN?
Yes, actually. There Are 2 Cisco switches in the way.
Regards,
Kari
On 15.11.2013 5:55, Cory Smelosky wrote:
Hello all,
I'm trying to get a MicroVAX II to cluster with MORIA. It's not going so
well:
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:48:59.18 %%%%%%%%%%%
Message from user SYSTEM on MOIRA
LANACP MOP V3 Downline Load Service
Volunteered to load request on ESA0 from MOYA
Requested file: DISK$MOIRA:<SYS10.>[SYSCOMMON.SYSLIB]NISCS_LOAD.EXE
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:49:04.72 %%%%%%%%%%%
Message from user SYSTEM on MOIRA
LANACP MOP V3 Downline Load Service
Load succeeded for MOYA on ESA0
System image, DISK$MOIRA:<SYS10.>[SYSCOMMON.SYSLIB]NISCS_LOAD.EXE (VAX
image)
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:50:58.07 %%%%%%%%%%%
22:50:58.07 Node MOIRA (csid 00010001) received VAXcluster membership
request from node MOYA
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:50:58.08 %%%%%%%%%%%
22:50:58.07 Node MOIRA (csid 00010001) proposed addition of node MOYA
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:50:58.62 %%%%%%%%%%%
22:50:58.61 Node MOIRA (csid 00010001) completed VAXcluster state
transition
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:51:07.99 %%%%%%%%%%%
22:51:07.99 Node MOIRA (csid 00010001) lost connection to node MOYA
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:51:27.59 %%%%%%%%%%%
22:51:27.49 Node MOIRA (csid 00010001) timed-out lost connection to node
MOYA
The moment it joins the cluster, it immediately loses connectivity.
There's between 5 and 10 milliseconds of latency between the two...but
that shouldn't matter...should it?
As I don't have a SCSI Qbus adapter, and I didn't get the TK50+TQK50 with
it, I can only MOP boot it. 60M disk is also not a lot.
.
Sent from mobile device that advertises itself for no good reason
On 15 Nov 2013, at 06:14, "Kari Uusim ki" <uusimaki at exdecfinland.org> wrote:
Hi Cory,
You don't happen to use a Cisco switch when you connect the MicroVAX to your LAN?
Yes, actually. There Are 2 Cisco switches in the way.
Regards,
Kari
On 15.11.2013 5:55, Cory Smelosky wrote:
Hello all,
I'm trying to get a MicroVAX II to cluster with MORIA. It's not going so
well:
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:48:59.18 %%%%%%%%%%%
Message from user SYSTEM on MOIRA
LANACP MOP V3 Downline Load Service
Volunteered to load request on ESA0 from MOYA
Requested file: DISK$MOIRA:<SYS10.>[SYSCOMMON.SYSLIB]NISCS_LOAD.EXE
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:49:04.72 %%%%%%%%%%%
Message from user SYSTEM on MOIRA
LANACP MOP V3 Downline Load Service
Load succeeded for MOYA on ESA0
System image, DISK$MOIRA:<SYS10.>[SYSCOMMON.SYSLIB]NISCS_LOAD.EXE (VAX
image)
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:50:58.07 %%%%%%%%%%%
22:50:58.07 Node MOIRA (csid 00010001) received VAXcluster membership
request from node MOYA
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:50:58.08 %%%%%%%%%%%
22:50:58.07 Node MOIRA (csid 00010001) proposed addition of node MOYA
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:50:58.62 %%%%%%%%%%%
22:50:58.61 Node MOIRA (csid 00010001) completed VAXcluster state
transition
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:51:07.99 %%%%%%%%%%%
22:51:07.99 Node MOIRA (csid 00010001) lost connection to node MOYA
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:51:27.59 %%%%%%%%%%%
22:51:27.49 Node MOIRA (csid 00010001) timed-out lost connection to node
MOYA
The moment it joins the cluster, it immediately loses connectivity.
There's between 5 and 10 milliseconds of latency between the two...but
that shouldn't matter...should it?
As I don't have a SCSI Qbus adapter, and I didn't get the TK50+TQK50 with
it, I can only MOP boot it. 60M disk is also not a lot.
Sent from mobile device that advertises itself for no good reason
On 15 Nov 2013, at 01:59, "Robert Jarratt" <robert.jarratt at ntlworld.com> wrote:
I had this recently and it turned out to be a misplaced card on the Qbus. In
other words not in the proper serpentine order. Check the Qbus sequence and
also try removing some cards.
I'll check that, thankS!
Qbus card ordering confuses me a bit.
Regards
Rob
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-
hecnet at Update.UU.SE] On Behalf Of Cory Smelosky
Sent: 15 November 2013 03:55
To: hecnet at update.uu.se
Subject: [HECnet] Cluster annoyances
Hello all,
I'm trying to get a MicroVAX II to cluster with MORIA. It's not going so
well:
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:48:59.18 %%%%%%%%%%%
Message from user SYSTEM on MOIRA LANACP MOP V3 Downline Load
Service Volunteered to load request on ESA0 from MOYA Requested file:
DISK$MOIRA:<SYS10.>[SYSCOMMON.SYSLIB]NISCS_LOAD.EXE
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:49:04.72 %%%%%%%%%%%
Message from user SYSTEM on MOIRA LANACP MOP V3 Downline Load
Service Load succeeded for MOYA on ESA0 System image,
DISK$MOIRA:<SYS10.>[SYSCOMMON.SYSLIB]NISCS_LOAD.EXE (VAX
image)
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:50:58.07 %%%%%%%%%%%
22:50:58.07 Node MOIRA (csid 00010001) received VAXcluster membership
request from node MOYA
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:50:58.08 %%%%%%%%%%%
22:50:58.07 Node MOIRA (csid 00010001) proposed addition of node MOYA
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:50:58.62 %%%%%%%%%%%
22:50:58.61 Node MOIRA (csid 00010001) completed VAXcluster state
transition
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:51:07.99 %%%%%%%%%%%
22:51:07.99 Node MOIRA (csid 00010001) lost connection to node MOYA
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:51:27.59 %%%%%%%%%%%
22:51:27.49 Node MOIRA (csid 00010001) timed-out lost connection to node
MOYA
The moment it joins the cluster, it immediately loses connectivity.
There's between 5 and 10 milliseconds of latency between the two...but
that
shouldn't matter...should it?
As I don't have a SCSI Qbus adapter, and I didn't get the TK50+TQK50 with
it, I
can only MOP boot it. 60M disk is also not a lot.
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Hi Cory,
You don't happen to use a Cisco switch when you connect the MicroVAX to your LAN?
Regards,
Kari
On 15.11.2013 5:55, Cory Smelosky wrote:
Hello all,
I'm trying to get a MicroVAX II to cluster with MORIA. It's not going so
well:
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:48:59.18 %%%%%%%%%%%
Message from user SYSTEM on MOIRA
LANACP MOP V3 Downline Load Service
Volunteered to load request on ESA0 from MOYA
Requested file: DISK$MOIRA:<SYS10.>[SYSCOMMON.SYSLIB]NISCS_LOAD.EXE
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:49:04.72 %%%%%%%%%%%
Message from user SYSTEM on MOIRA
LANACP MOP V3 Downline Load Service
Load succeeded for MOYA on ESA0
System image, DISK$MOIRA:<SYS10.>[SYSCOMMON.SYSLIB]NISCS_LOAD.EXE (VAX
image)
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:50:58.07 %%%%%%%%%%%
22:50:58.07 Node MOIRA (csid 00010001) received VAXcluster membership
request from node MOYA
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:50:58.08 %%%%%%%%%%%
22:50:58.07 Node MOIRA (csid 00010001) proposed addition of node MOYA
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:50:58.62 %%%%%%%%%%%
22:50:58.61 Node MOIRA (csid 00010001) completed VAXcluster state
transition
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:51:07.99 %%%%%%%%%%%
22:51:07.99 Node MOIRA (csid 00010001) lost connection to node MOYA
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:51:27.59 %%%%%%%%%%%
22:51:27.49 Node MOIRA (csid 00010001) timed-out lost connection to node
MOYA
The moment it joins the cluster, it immediately loses connectivity.
There's between 5 and 10 milliseconds of latency between the two...but
that shouldn't matter...should it?
As I don't have a SCSI Qbus adapter, and I didn't get the TK50+TQK50 with
it, I can only MOP boot it. 60M disk is also not a lot.
CHIMPY Retro Tetris Update:
Mark Wickens is in the lead with a score of 7,640, followed by Vilaca with 1,574 (score not verified with screenshot so might not count).
Guys, we're still running until 23:59:00 GMT on 31-DEC-2013 so there's plenty of time to win random Arabic money AND certificates of Tetris awesomeness.
Telnet to CHIMPY.SAMPSA.COM or SET HOST CHIMPY, log in as TETRIS.
REMEMBER TO SCREENSHOT YOUR RESULT IF YOU GET A NEW HIGHSCORE. Or at least write down what date/time/node you came from if SET HOST, so I can verify the score..
sampsa <sampsa at mac.com>
mobile +358 40 7208932
I had this recently and it turned out to be a misplaced card on the Qbus. In
other words not in the proper serpentine order. Check the Qbus sequence and
also try removing some cards.
Regards
Rob
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-
hecnet at Update.UU.SE] On Behalf Of Cory Smelosky
Sent: 15 November 2013 03:55
To: hecnet at update.uu.se
Subject: [HECnet] Cluster annoyances
Hello all,
I'm trying to get a MicroVAX II to cluster with MORIA. It's not going so
well:
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:48:59.18 %%%%%%%%%%%
Message from user SYSTEM on MOIRA LANACP MOP V3 Downline Load
Service Volunteered to load request on ESA0 from MOYA Requested file:
DISK$MOIRA:<SYS10.>[SYSCOMMON.SYSLIB]NISCS_LOAD.EXE
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:49:04.72 %%%%%%%%%%%
Message from user SYSTEM on MOIRA LANACP MOP V3 Downline Load
Service Load succeeded for MOYA on ESA0 System image,
DISK$MOIRA:<SYS10.>[SYSCOMMON.SYSLIB]NISCS_LOAD.EXE (VAX
image)
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:50:58.07 %%%%%%%%%%%
22:50:58.07 Node MOIRA (csid 00010001) received VAXcluster membership
request from node MOYA
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:50:58.08 %%%%%%%%%%%
22:50:58.07 Node MOIRA (csid 00010001) proposed addition of node MOYA
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:50:58.62 %%%%%%%%%%%
22:50:58.61 Node MOIRA (csid 00010001) completed VAXcluster state
transition
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:51:07.99 %%%%%%%%%%%
22:51:07.99 Node MOIRA (csid 00010001) lost connection to node MOYA
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:51:27.59 %%%%%%%%%%%
22:51:27.49 Node MOIRA (csid 00010001) timed-out lost connection to node
MOYA
The moment it joins the cluster, it immediately loses connectivity.
There's between 5 and 10 milliseconds of latency between the two...but
that
shouldn't matter...should it?
As I don't have a SCSI Qbus adapter, and I didn't get the TK50+TQK50 with
it, I
can only MOP boot it. 60M disk is also not a lot.
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
