I just increased the memory on one of my SIMH VAX VM's to 512 MB from 64 MB - the system boots fine but SHOW MEMORY (under OpenVMS 7.3-1) still reports 64 MB.
Do I need to tell the VMS installation about the new RAM somehow? How much RAM does 7.3-1 (VAX) support anyway?
Sampsa
Guys,
On the same note, my network will be disconnected some time in the near future, I've ordered a change to my DSL service (moving from two lines and a load balanced router to a single bonded connection - should increase down and uplink speeds by roughly a factor of 2).
At the moment I've only got a bridge connection to update, but anyone relying on GORVAX's MULTINET tunnel will experience some (hopefully minimal) downtime.
Sampsa
On Wed, Nov 17, 2010 at 4:53 AM, Pontus Pihlgren <pontus at update.uu.se> wrote:
Hi All.
There is some planned downtime in the university network that will
probably make mim.update.uu.se and anything else running under
update.uu.se unavailable from midnight til morning on the 24:th of
november.
If you read swedish:
http://uadm.uu.se/iti/it-drift/Driftavbrott
Notice that I have no control over this, I'm just the messenger.
Regards,
Pontus
Hello!
Thank you for advising us. I'm not the sort to "Stun the messenger
because he's the messenger." sort.... But it will cause an upset.
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
Hi All.
There is some planned downtime in the university network that will
probably make mim.update.uu.se and anything else running under
update.uu.se unavailable from midnight til morning on the 24:th of
november.
If you read swedish:
http://uadm.uu.se/iti/it-drift/Driftavbrott
Notice that I have no control over this, I'm just the messenger.
Regards,
Pontus
On 12 Nov 2010, at 04:43, Bob Armstrong wrote:
Chrissie Caulfield wrote:
The thing to do is to upgrade dnprogs.
Thanks, Chrissie - good point. I downloaded the latest source tarball from
http://packages.debian.org/source/sid/all/dnprogs
and recompiled everything under lenny. [I must say that the recompile was
pretty painless as these things go.]
Now I have
ziti:/home/bob# dnroute -V
dnroute from dnprogs version 2.55
A few things appear different, but sadly dnroute still segfaults after
starting Multinet
ziti:/home/bob# dmesg | grep -i dnroute
[ 94.112034] dnroute[2996]: segfault at 0 ip 0804ac18 sp bfc40f70
error 4 in dnroute[8048000+6000]
I notice that the Multinet daemon no longer prints the address of the
adjacent node as it did before - don't know if that's significant or if that
behavior was just removed. And I also notice that the Multinet daemon now
exits (silently, without any message, good, bad or indifferent) shortly
after it's started (and presumably shortly after dnroute goes Tango
Uniform).
Is there a plan B?
I don't have a plan B sorry.
As I mentioned some time ago, I don't have the resources to maintain DECnet any more :-(
Chrissie
Chrissie Caulfield wrote:
The thing to do is to upgrade dnprogs.
Thanks, Chrissie - good point. I downloaded the latest source tarball from
http://packages.debian.org/source/sid/all/dnprogs
and recompiled everything under lenny. [I must say that the recompile was
pretty painless as these things go.]
Now I have
ziti:/home/bob# dnroute -V
dnroute from dnprogs version 2.55
A few things appear different, but sadly dnroute still segfaults after
starting Multinet
ziti:/home/bob# dmesg | grep -i dnroute
[ 94.112034] dnroute[2996]: segfault at 0 ip 0804ac18 sp bfc40f70
error 4 in dnroute[8048000+6000]
I notice that the Multinet daemon no longer prints the address of the
adjacent node as it did before - don't know if that's significant or if that
behavior was just removed. And I also notice that the Multinet daemon now
exits (silently, without any message, good, bad or indifferent) shortly
after it's started (and presumably shortly after dnroute goes Tango
Uniform).
Is there a plan B?
Thanks again,
Bob
Hiya
The thing to do is to upgrade dnprogs. Version 2.45 has a changelog entry that says "fix crash in dnroute daemon"
;-)
The latest version is 2.55
Chrissie
On 11 Nov 2010, at 19:12, Bob Armstrong wrote:
I've used Linux DECnet successfully with local Ethernet connections, but
now I'm trying to set up a Multinet link and dnroute segfaults every time I
start the Multinet link. Of course, Multinet may have nothing to do with it
- all the hosts in on my local network are in the same area and so when
Multinet starts it's also the first time dnroute ever sees another level 2
routing node.
The host is Debian/Lenny -
bob at ziti:~$ uname -a
Linux ziti 2.6.29.3-ziti.4 #1 Sun Nov 7 20:38:06 PST 2010 i586
GNU/Linux
The dnprogs package is v2.44
bob at ziti:~$ /usr/sbin/dnroute -V
dnroute from dnprogs version 2.44
The /etc/default/decnet file says
bob at ziti:~$ cat /etc/default/decnet
# DECnet configuration for ZITI - RLA [8-Nov-2010]
DNET_INTERFACES="eth0"
DNET_DAEMONS="dnetd dnroute"
dnroute_FLAGS="-v -2"
ROUTING=2
PRIORITY=16
(Note that Multinet is not started in here - for the time being, I'm
starting it manually...)
ziti:/home/bob# ps aux | grep -i dnroute
root 2993 0.0 0.2 1672 548 ? Ss 10:42 0:00
/usr/sbin/dnroute -v -2
ziti:/home/bob# dnetinfo
Addr Dev
2.1 LEGATO eth0
2.16 ziti! lo
ziti:/home/bob# multinet 2.16 192.108.200.211 &
using tun device tap0
Remote address = 59.58 (60474)
ziti:/home/bob# dmesg | grep -i dnroute
[ 383.364356] dnroute[2997]: segfault at 0 ip 0804ac18 sp bfaa3ca0
error 4 in dnroute[8048000+6000]
Any ideas what I'm doing wrong? Hopefully it's something easy :-)
Thanks,
Bob Armstrong
I've used Linux DECnet successfully with local Ethernet connections, but
now I'm trying to set up a Multinet link and dnroute segfaults every time I
start the Multinet link. Of course, Multinet may have nothing to do with it
- all the hosts in on my local network are in the same area and so when
Multinet starts it's also the first time dnroute ever sees another level 2
routing node.
The host is Debian/Lenny -
bob at ziti:~$ uname -a
Linux ziti 2.6.29.3-ziti.4 #1 Sun Nov 7 20:38:06 PST 2010 i586
GNU/Linux
The dnprogs package is v2.44
bob at ziti:~$ /usr/sbin/dnroute -V
dnroute from dnprogs version 2.44
The /etc/default/decnet file says
bob at ziti:~$ cat /etc/default/decnet
# DECnet configuration for ZITI - RLA [8-Nov-2010]
DNET_INTERFACES="eth0"
DNET_DAEMONS="dnetd dnroute"
dnroute_FLAGS="-v -2"
ROUTING=2
PRIORITY=16
(Note that Multinet is not started in here - for the time being, I'm
starting it manually...)
ziti:/home/bob# ps aux | grep -i dnroute
root 2993 0.0 0.2 1672 548 ? Ss 10:42 0:00
/usr/sbin/dnroute -v -2
ziti:/home/bob# dnetinfo
Addr Dev
2.1 LEGATO eth0
2.16 ziti! lo
ziti:/home/bob# multinet 2.16 192.108.200.211 &
using tun device tap0
Remote address = 59.58 (60474)
ziti:/home/bob# dmesg | grep -i dnroute
[ 383.364356] dnroute[2997]: segfault at 0 ip 0804ac18 sp bfaa3ca0
error 4 in dnroute[8048000+6000]
Any ideas what I'm doing wrong? Hopefully it's something easy :-)
Thanks,
Bob Armstrong
Hello!
November question time. I have here a virtual system, running Windows
Server 2003, naturally its biggest problem is that of its also running
on top of an OS from the same firm as the virtual system frame, but
that's besides the point. (We can trade those insults off list later.)
Now the question, "Has anyone managed to get the latest release of E11
running that way with, any of the operating systems who support
Ethernet?", and then following that, "What suggestions are available
for making it available via a dynamically assigned name and IP address
to the network?".
My ISP seems to want to deliver an IP address to me via PPPoE for
normal commercial DSL, I once asked about a static IP address, but the
service hid behind some outlandish reason at the time that it wasn't
possible. I suspect its because the ISP, then Covad behind AT&T, never
considered such a method of delivery for its commercial, read
household, customers, and hence went ahead with what it believed to be
an easy method. Then in March I migrated from that method of having a
ISP to work with to just Covad. Same other e-mail addresses naturally.
To supply the occasional access method for the systems, for when I was
away from here, and needed to do so, I went ahead and used the
services of DDNS to make a hostname available. I chose the vendor
http://www.dyndns.com/ simply because it would be an easy
configuration step, then, or so I thought.
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
