Correct me if I'm wrong (which is likely), but doesn't DECnet (at least the Cisco variant) resolve routing ties between area routers by using the highest numbered one? Maybe your area routers should be at the top end of the address range?
This Cisco document says "End systems send routing requests to a designated Level 1 router. The Level 1 router with the highest priority is elected to be the designated router. If two routers have the same priority, the one with the larger node number becomes the designated router. A router's priority can be manually configured to force it to become the designated router."
http://www.cisco.com/en/US/docs/internetworking/troubleshooting/guide/tr191…
(please excuse me if I'm totally off base)
Ian
On 2013-01-08, at 2:26 PM, Cory Smelosky <b4 at gewt.net> wrote:
Hello!
The current way I allocate node numbers is in sequential order and it's getting tremendously messy and difficult to manage, so I am going to come up with a plan to divide things more cleanly and I'm looking for feedback.
I'm thinking: 9.1-9.21 for administration/control purposes (area routers and so forth), subdividing the area in to geographic areas (areas of ~250 each initially, the others can be further subdivided as needed), and then subdividing those geographic regions by purpose.
so:
(apologies about this chart being absolutely atrocious and useless, it functioned largely as stress relief)
9.1-9.21
|
V relief
OHIO (9.22-9.271)-----|----------------|-------------------|
| | | | |
V V V V V
(VMS) (PDP-11) (PDP-10) (OTHER) (WORKSTATION)
9. (22-.72) (73-123) (124-174) (175-225) (226-278)
And repeat for other regions.
Should I subdivide further?
What could I use instead of OTHER?
Should I break up the area differently?
Further suggestions?
Should I put physical hardware as a sub-sub-subdivision, its own tertiary level (in place of OTHER), or not differentiate them at all?
Let me know your thoughts.
---
Filter service subscribers can train this email as spam or not-spam here
I have fiche from the 3.x era if I remember correctly.
Regards
Rob
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
On Behalf Of Dave McGuire
Sent: 08 January 2013 19:59
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Re: VMS sources
On 01/08/2013 02:55 PM, Cory Smelosky wrote:
I've always wondered about VMS sources: how they are actually
distributed today and how much space they take? Is a CD-ROM enough
for everything? And in which format are they? Just simple text files
in a bunch of directories or there is something fancier such as some
cross references and indexes?
They used to make source *listings* available on fiche; I have
several sets of those. It's a stack of fiche maybe 3-4" thick.
How old are these "listings"?
I haven't looked at them in years, but I think I have at least 5.1 and
5.2,
possibly 4.7.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 1/8/2013 9:01 PM, Peter Lothberg wrote:
Set up a (cisco) tunnel to 130.238.19.60 (and tell me your side IP
address).
I think it's time to come up with something a little better to track all these.
Thoughts?
-brian
Hello!
The current way I allocate node numbers is in sequential order and it's getting tremendously messy and difficult to manage, so I am going to come up with a plan to divide things more cleanly and I'm looking for feedback.
I'm thinking: 9.1-9.21 for administration/control purposes (area routers and so forth), subdividing the area in to geographic areas (areas of ~250 each initially, the others can be further subdivided as needed), and then subdividing those geographic regions by purpose.
so:
(apologies about this chart being absolutely atrocious and useless, it functioned largely as stress relief)
9.1-9.21
|
V relief
OHIO (9.22-9.271)-----|----------------|-------------------|
| | | | |
V V V V V
(VMS) (PDP-11) (PDP-10) (OTHER) (WORKSTATION)
9. (22-.72) (73-123) (124-174) (175-225) (226-278)
And repeat for other regions.
Should I subdivide further?
What could I use instead of OTHER?
Should I break up the area differently?
Further suggestions?
Should I put physical hardware as a sub-sub-subdivision, its own tertiary level (in place of OTHER), or not differentiate them at all?
Let me know your thoughts.
Speaking of copyright notices in DEC software... The standard one included this paragraph:
; THE INFORMATION IN THIS DOCUMENT IS SUBJECT TO CHANGE WITHOUT NOTICE
; AND SHOULD NOT BE CONSTRUED AS A COMMITMENT BY DIGITAL EQUIPMENT
; CORPORATION. DIGITAL EQUIPMENT CORPORATION ASSUMES NO RESPONSIBILITY
; FOR ANY ERRORS THAT MAY APPEAR IN THIS DOCUMENT.
But I have a copy of a manual (the RSTS V4 kernel ODT manual), which seems to be really an internal document though I got it outside DEC, which has this spoof:
THE MATERIAL INCLUDED IN THIS DOCUMENT, LIMITED TO
BUT NOT INCLUDING, CONSTRUCTION SPEEDS AND OPERATING
PURPOSES IS FOR INSTRUCTION TIMES ONLY. ALL SUCH
CLAIM IS MATERIAL WITHOUT NOTICE, AND IS BOUND TO
CHANGE THE SUBJECT.
:-)
paul
On Tue, Jan 8, 2013 at 4:36 PM, Cory Smelosky <b4 at gewt.net> wrote:
Each with a different license, each with different terms...
but if it was a "real UNIX" had one of the AT&T licenses (which as you point there were many ;-)
On Tue, Jan 8, 2013 at 4:33 PM, <Paul_Koning at dell.com> wrote:
it only means that the IP owners didn't find it worth the trouble to enforce the software license.
Fair enough. But it was standard practice. I have not idea if Xerox paid DEC for the licenses for the compiler and other tools suite for their PDP-10 clone at PARC. It possible they just shied away from anything with such a copyright notice, and could because like UNIX today, all of the research community was using PDP-10s (which is why they wanted one at PARC) and there were "open source" and "free" compilers that the DARPA had paid for coming out Stanford, CMU, MIT and the like. I never used that machine, but I certainly new of it.
By the mid late 1970s, I did use an Alto, and the SW we were running on it by that time was Xerox created. But one of it's designers is an old friend (and officemate) and he used to say their had been a lot of Nova code running on the Altos. How much did the use from DG, again I do not know.
I do know the Amdahl's ran IBM code. IBM had just been sued about "bundling" SW so, it possible they ignored it a bit because they were being chased from the Justice Dept WRT monopoly and just decided it was not worth trying to enforce it.
On 8 Jan 2013, at 16:33, <Paul_Koning at Dell.com> wrote:
On Jan 8, 2013, at 4:10 PM, Clem Cole wrote:
On Tue, Jan 8, 2013 at 3:20 PM, <Paul_Koning at dell.com> wrote:
What DEC and others did is to provide listings you could read, but you weren't allowed to use or modify the code. Sources, maybe, but even then I don't think you could hand the resulting executable bits to anyone outside your organization.
I think you are split hairs a little.
...
Simple put, in the late 1960s and early 1970s, different firms make sold "clones" of different machines that used the original developers code base. The "cloners" made the market bigger and sometimes (like Foonly) could serve a need the primary manufacturer was not going to supply.
True. And they often got away with that. That doesn't mean the licenses permitted it -- it only means that the IP owners didn't find it worth the trouble to enforce the software license. A possible reason is that there wasn't much case history for software IP, while there was already a lot of case history for device patents, so attacking a cloner via patent rights was easier and more reliable.
But even as far back as 1974 you'd find source code with headers saying things like this:
; THE SOFTWARE DESCRIBED IN THIS DOCUMENT IS FURNISHED TO THE PURCHASER
; UNDER A LICENSE FOR USE ON A SINGLE COMPUTER SYSTEM AND CAN BE COPIED
; (WITH INCLUSION OF DIGITAL'S COPYRIGHT NOTICE) ONLY FOR USE IN SUCH
; SYSTEM, EXCEPT AS MAY OTHERWISE BE PROVIDED IN WRITING BY DIGITAL.
which pretty clearly tells cloners to go away. Again, that doesn't mean it was uniformly enforced, but it does mean that was the stated restriction. Certainly this is nothing like open source.
Unix of course is a very different beast.
You mean beasts. ;)
You have just so many to choose from Each with a different license, each with different terms...
paul
On Jan 8, 2013, at 4:10 PM, Clem Cole wrote:
On Tue, Jan 8, 2013 at 3:20 PM, <Paul_Koning at dell.com> wrote:
What DEC and others did is to provide listings you could read, but you weren't allowed to use or modify the code. Sources, maybe, but even then I don't think you could hand the resulting executable bits to anyone outside your organization.
I think you are split hairs a little.
...
Simple put, in the late 1960s and early 1970s, different firms make sold "clones" of different machines that used the original developers code base. The "cloners" made the market bigger and sometimes (like Foonly) could serve a need the primary manufacturer was not going to supply.
True. And they often got away with that. That doesn't mean the licenses permitted it -- it only means that the IP owners didn't find it worth the trouble to enforce the software license. A possible reason is that there wasn't much case history for software IP, while there was already a lot of case history for device patents, so attacking a cloner via patent rights was easier and more reliable.
But even as far back as 1974 you'd find source code with headers saying things like this:
; THE SOFTWARE DESCRIBED IN THIS DOCUMENT IS FURNISHED TO THE PURCHASER
; UNDER A LICENSE FOR USE ON A SINGLE COMPUTER SYSTEM AND CAN BE COPIED
; (WITH INCLUSION OF DIGITAL'S COPYRIGHT NOTICE) ONLY FOR USE IN SUCH
; SYSTEM, EXCEPT AS MAY OTHERWISE BE PROVIDED IN WRITING BY DIGITAL.
which pretty clearly tells cloners to go away. Again, that doesn't mean it was uniformly enforced, but it does mean that was the stated restriction. Certainly this is nothing like open source.
Unix of course is a very different beast.
paul
Clem Cole <clemc at ccc.com> writes:
--e89a8f64310498553304d2cd77d8 Content-Type: text/plain;
charset=ISO-8859-1
On Tue, Jan 8, 2013 at 3:55 PM, Brian Schenkenberger, VAXman- <
system at tmesis.com> wrote:
The "listing" portion is far more valuable than the source > itself. >
Amen - although I might say - "was often more valuable" -- if you had
a bug needed to fix it fast, the key you could (which is the cry of the
FOSS movement). You did not have to wait for the vendor.
But more often than note, the reason you wanted to see the source was to
understand a behavior what was happening that did not make sense.
Sometimes, you might find a bug, but more often than not, I might find a
way to do what i wanted to do with what I had in hand,
I recently (well OK, 9 months ago) discovered a day-one bug in the OpenVMS
Itanium primitives for self-relative queue manipulation. While I have the
source listings, I found it far easier to explore what was happening using
the "poor-man's microfiche" and ANALYZE/CRASH. I wrote an extensive blog
on it. It was one of the last bugs that Clair Grant worked before he was
made an OpenVMS Engineering outcast. :( Point is that with the right tool,
you can figure out what's going on. In the days of the listings on fiche,
I found it often much easier to look at the code in SDA than to lug about
the fiche reader and ruin my eyesight.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
