| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: ZC/2-status |
VD> CS> Sorry, I was thinking you knew. There's a specification out there that
VD> CS> by design actually assigns netnumbers to regions.
VD>Where it is write - FTS, Policy or another official document?
Netnumbers to regions? FTS I think. I'm not totally sure. Once in a
while it comes up.
VD> CS> In Z6, RC's start with 6:6#/# and in Z1 they are 1:1#/# but it varies
VD> CS> outside that a bit.
VD>Now these zones very small, and theirs regions have not
VD>more 20 sysops (in middle)... Regions on Z2 have from 1 to
True, but the discussion was on the overall design system that has been
used, not the actual size.
VD>near 4500 sysops, in middle - 100 nodes per region.
VD>Arithmetic: our region's count of sysops (4500) divide by
VD>100 (nodes per region) - result 45 regions. If divide by 20
VD>(as other zones) - result 225 regions (very large! It is
VD>impossible for control!).
Well, I'd start thinking small and work around as needed. I'd tend to
start with 10 if starting a new Z7. There will be enough trouble just
splitting that way. Sees more 'do-able' to me looking in from the
outside and considering the task.
xxcarol
* OLX 2.1 TD * Unable to locate Coffee -- Operator Halted!
--- Maximus/NT 3.01
* Origin: Owl's Anchor (1:261/1466)SEEN-BY: 633/267 270 5030/786 @PATH: 261/1466 123/500 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.