On Dec 23, 2012, at 12:37 AM, John Wilson wrote:
From: <Paul_Koning at Dell.com>
FWIW, DMC and DMR are the same at the programmer level.
(Except for some trivial differences.) My notes say the limit on outstanding
TX or RX buffers is 7 for DMC vs. 64 for DMR. Also, BSEL3 is a read/write
reg that survives master clears on DMC but gives diag completion status on
DMR (which is how INIT.SYS tells them apart). And opcode 02 is HALTR on
DMR and reserved on DMC. Is there other stuff?
I didn't know of those details, or other differences that matter to a driver. The way I've seen it done is that a DMC driver (7 buffers max) works fine for DMR, and there wasn't any real reason to do DMR-specific things.
They are somewhat different at the protocol level -- DMC uses an older
version of DDCMP and has some bugs in that implementation, especially in
the "high speed" (1 Mb/s) version.
Buggy WRT dealing with correct implementations, or buggy even talking to
each other? Just curious (I have a pair of them around here somewhere).
Buggy in the sense of not being 100% compliant to the DDCMP spec as written. They talk fine to each other. If you want to have another DDCMP implementation talk to them, you have to be aware of those details. I don't remember them but can find them if needed -- they would be in the NODVR (software DDCMP) RSTS/E driver sources.
paul
Well, I'n just VMS oriented. What happens if you run nslookup at it and
Set q=soa
Ls (yourdomain)
------Origineel bericht------
Van: sampsa at mac.com
Afzender: owner-hecnet at Update.UU.SE
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] MULTINET borks due to broken Bind9 setup?
Verzonden: 23 december 2012 17:56
Linux, specifically Ubuntu 12, using bind9.
Sampsa
On 23 Dec 2012, at 18:55, hvlems at zonnet.nl wrote:
On what OS?
------Origineel bericht------
Van: sampsa at mac.com
Afzender: owner-hecnet at Update.UU.SE
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: [HECnet] MULTINET borks due to broken Bind9 setup?
Verzonden: 23 december 2012 17:20
Any Bind gurus out here?
Can you contact me off list, having problem with reverse zones...
Sampsa
Linux, specifically Ubuntu 12, using bind9.
Sampsa
On 23 Dec 2012, at 18:55, hvlems at zonnet.nl wrote:
On what OS?
------Origineel bericht------
Van: sampsa at mac.com
Afzender: owner-hecnet at Update.UU.SE
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: [HECnet] MULTINET borks due to broken Bind9 setup?
Verzonden: 23 december 2012 17:20
Any Bind gurus out here?
Can you contact me off list, having problem with reverse zones...
Sampsa
On what OS?
------Origineel bericht------
Van: sampsa at mac.com
Afzender: owner-hecnet at Update.UU.SE
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: [HECnet] MULTINET borks due to broken Bind9 setup?
Verzonden: 23 december 2012 17:20
Any Bind gurus out here?
Can you contact me off list, having problem with reverse zones...
Sampsa
Speaking of Modula-2, I have an incomplete Modula-2 for RSX. Anyone else
have the missing bits and pieces?
Don't know what bits you're looking for, but somewhere I have Modula-2 for
VMS. It's all written in Modula-2, of course.
Bob
Can you contact me off list, having problem with reverse zones...
I'll take a crack at it if you want; what's the error, and what does the
zone file look like?
De
On 2012-12-23 12:28, sampsa at mac.com wrote:
I managed to crash the server I'm running the bridge on and now have rebuilt another, however the bridge seems to not work.
Is this config right:
--- snip ---
local eth0
update psilo.update.uu.se:4711
j
[decnet]
local
update
[lat]
local
update
-- snip ---
Mainly wondering if the address for update is correct...
Yep.
(But what is that "j" doing there?)
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
I managed to crash the server I'm running the bridge on and now have rebuilt another, however the bridge seems to not work.
Is this config right:
--- snip ---
local eth0
update psilo.update.uu.se:4711
j
[decnet]
local
update
[lat]
local
update
-- snip ---
Mainly wondering if the address for update is correct...