On Wed, Jun 4, 2014 at 6:50 AM, Peter Lothberg <roll at stupi.se> wrote:
Out of the configured tunnels from the Cisco in Uppsala, there is only one
active tunnel not to area59....
interface Tunnel1099
description tunnel to Mark G Thomas <mark at misty.com> (Area 23)
no ip address
logging event subif-link-status
decnet cost 10
tunnel source Ethernet0
tunnel destination 71.246.8.102
is it safe to remove the rest, assuming they are "historical"?
Hi Peter,
The other tunnels are all up:
a12rtr>show decnet neigh
Net Node Interface MAC address Flags
0 9.1023 Tunnel52 0000.0000.0000 A
0 23.1023 Tunnel59 0000.0000.0000 A
0 42.1022 Tunnel51 0000.0000.0000 A
0 52.1023 Tunnel50 0000.0000.0000 A
0 61.1023 Tunnel53 0000.0000.0000 A
0 12.2 FastEthernet0/0 aa00.0400.0230
0 12.3 FastEthernet0/0 aa00.0400.0330
My tunnels to you have been administratively shutdown as they have never been up before. The tunnel to Mark Darvill does not appear to be working correctly at the moment, he likely sorting out his network or configuration.
For interests sake I have just set all the tunnel interfaces to you to "no shutdown". Here is the configuration in my router for the tunnels to you:
interface Tunnel54
description HECnet tunnel for Peter Lothberg Reston VA (Area 59) [Version:218]
no ip address
decnet cost 20
tunnel source FastEthernet0/0
tunnel destination 199.0.131.2
tunnel path-mtu-discovery
!
interface Tunnel55
description HECnet tunnel for Peter Lothberg Stockholm Sweden (Area 59) [Version:218]
no ip address
decnet cost 20
tunnel source FastEthernet0/0
tunnel destination 192.108.200.213
tunnel path-mtu-discovery
!
interface Tunnel56
description HECnet tunnel for Peter Lothberg Uppsala (Area 59) [Version:218]
no ip address
decnet cost 20
tunnel source FastEthernet0/0
tunnel destination 130.238.19.60
tunnel path-mtu-discovery
!
Regards, Tim.
Out of the configured tunnels from the Cisco in Uppsala, there is only one
active tunnel not to area59....
interface Tunnel1099
description tunnel to Mark G Thomas <mark at misty.com> (Area 23)
no ip address
logging event subif-link-status
decnet cost 10
tunnel source Ethernet0
tunnel destination 71.246.8.102
is it safe to remove the rest, assuming they are "historical"?
-P
On 4 Jun 2014, at 00:58, Jordi Guillaumes i Pons <jg at jordi.guillaumes.name> wrote:
My personal experience with the RaspPi and the SD cards is the card slot in the Pi brokes with ease, so I avoid switching the cards as much as posible. Any minimal lost of contact between the card and the slot leads to a corrupted and (usually) unrecoverable filesystem, so my VAXen are in a real HD, and my cards are really microSDs inserted into an adapter, which is inserted into the Pi and is never moved out.
Hmm, never actually changed the SD card in my Pi, it's sort of a fire-and-forget device for me, seems very reliable though (uptime = 334 days, and the last reboot was due to a power outage) - aside from the physical problems you pointed out..
El 03/06/2014, a les 23.30, Sampsa Laine <sampsa at mac.com> va escriure:
I can second that, HPIVAX has been up for like 18 months, no problems whatsoever.
Sampsa
My personal experience with the RaspPi and the SD cards is the card slot in the Pi brokes with ease, so I avoid switching the cards as much as posible. Any minimal lost of contact between the card and the slot leads to a corrupted and (usually) unrecoverable filesystem, so my VAXen are in a real HD, and my cards are really microSDs inserted into an adapter, which is inserted into the Pi and is never moved out.
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
On 3 Jun 2014, at 22:54, Vern Brownell <vern at brownell.com> wrote:
Hi Fred,
I ve been running SIMH with OpenVMS 7.3 on a Pi for over a year now and it has been rock solid. Just checked with SH SYS, it s been up for 224 days straight with a fair amount of daily activity and no noticeable degradation in performance. Runs more reliably than my AXP hardware. FWIW YMMV.
And 8GB SD cards are now about $5 on AMZN.
Best of luck,
I can second that, HPIVAX has been up for like 18 months, no problems whatsoever.
Sampsa
El 03/06/2014, a les 21.38, Fred <fcoffey at misernet.net> va escriure:
For those of you who are running SIMH on Raspberry Pi, how are you getting around the fact that lots of writes on your SD card will eventually trash it? I am considering moving my VAX instance to my Raspi, but didn't want to eat an SD card ... ;)
Is it as simple as perhaps mounting the VAX .dsk via NFS and letting SIMH use that, instead of the card?
I'm using an USB disk for the emulators (actually, all my rootfs is in that disk). On my "testing" raspi I mount an NFS partition, just as you said.
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
Hi Fred,
I ve been running SIMH with OpenVMS 7.3 on a Pi for over a year now and it has been rock solid. Just checked with SH SYS, it s been up for 224 days straight with a fair amount of daily activity and no noticeable degradation in performance. Runs more reliably than my AXP hardware. FWIW YMMV.
And 8GB SD cards are now about $5 on AMZN.
Best of luck,
Vern
On Jun 3, 2014, at 12:38 PM, Fred <fcoffey at misernet.net> wrote:
Hi all,
For those of you who are running SIMH on Raspberry Pi, how are you getting around the fact that lots of writes on your SD card will eventually trash it? I am considering moving my VAX instance to my Raspi, but didn't want to eat an SD card ... ;)
Is it as simple as perhaps mounting the VAX .dsk via NFS and letting SIMH use that, instead of the card?
Thanks,
Fred
----
Lets call it for what it is - "legacy" is a term that people use in a
polite but derogatory manner to imply that the future direction they
prefer is not that which they view as the current direction.
On Jun 3, 2014, at 3:38 PM, Fred <fcoffey at misernet.net> wrote:
Hi all,
For those of you who are running SIMH on Raspberry Pi, how are you getting around the fact that lots of writes on your SD card will eventually trash it? I am considering moving my VAX instance to my Raspi, but didn't want to eat an SD card ... ;)
It s worth doing the experiment to see whether (and when) this is a problem in practice. Flash storage devices like SD cards do wear leveling , and if that s implemented reasonably well, you can get a lot of life out of a card. The other consideration is that they only cost a couple of dollars, so why worry about it (given adequate backup)?
paul
Hi all,
For those of you who are running SIMH on Raspberry Pi, how are you getting around the fact that lots of writes on your SD card will eventually trash it? I am considering moving my VAX instance to my Raspi, but didn't want to eat an SD card ... ;)
Is it as simple as perhaps mounting the VAX .dsk via NFS and letting SIMH use that, instead of the card?
Thanks,
Fred
----
Lets call it for what it is - "legacy" is a term that people use in a
polite but derogatory manner to imply that the future direction they
prefer is not that which they view as the current direction.
>John Wilson wrote:
V7.1 of Ersatz-11 is done. New features include:
- DMP11/DMV11 network ports.
- DDCMP over TCP and UDP (as well as serial lines).
- Kermit client for transferring files in and out of the PDP-11 over any
emulated serial line (KERMIT command and KERMIT: pseudo-driver).
- "MOUNT ddcu: BAD: /LIST:badblks.txt ..." adds fake bad blocks (from a
list in a file) to any disk (for testing PDP-11 utilities).
- "MOUNT ddcu: ... {/NOPAD | /PAD:NULL | /PAD:RAM}" selects how to handle
emulating disks with an image file (or physical drive) that's smaller
than the drive being emulated. (/PAD:RAM is currently an experimental
feature and may have bugs -- it's intended for systems that use the tail
end of the drive as swap space.)
- DPDISK: and DPTAPE: (BOTH UNSUPPORTED) set up dual-ported disks and tapes.
Any disk or tape type can be mounted on one of these pseudo-devices, after
which units 0 and 1 of the pseudo-device represent the two ports which may
in turn each be mounted on different PDP-11 controllers, presumably on
different processors of a multi-processor system.
- "SET TTu: DL11A" (needed by DOS/BATCH for TT0:).
Impressive list of new features!! As usual, congratulations for a
job well done.
- "SET PCLOG n" enlarges the number of logged PC values that can be shown
with SHOW PCLOG.
This will be the big one for me as I want to be able to check it against
a similar (NEWLY added) feature in SDHX.SYS for RT-11. Of course,
your PCLOG adds only about 8% to 10% additional time. In SD:,
my initial benchmark suggests at least a HUNDRED times longer.
In addition, for SDHX.SYS, the current size of the PC Address
circular buffer is only 3000 PC Addresses which, although much
larger than the original 64, can't compete against a VERY large "n".
- New native "SYS" utilities for Linux, OS/2, and Windows, for making disks
(or flash drives) boot the stand-alone version of E11. The Linux and
Windows versions try to notice if a drive (e.g. USB flash card that came
pre-partitioned) hasn't been made "active" and/or is missing the MBR
bootstrap, and fixes it (may require privs). If anyone can please tell
me what sys calls in OS/2 will find out which physical drive owns a FAT
volume given the drive letter, I'd appreciate it!
- The stand-alone version's bootstrap supports USB drives (including flash).
Also there's a bootable CD, but since there's currently no ATAPI dev
driver or ISO9660 FS driver, it can't install E11 onto a hard drive, and
it requires a FAT volume to hold .DSK files etc. So it's more of a proof
of concept than something useful (but it's an easy way to try out the
stand-alone version of E11).
Bug fixes and tweaks as usual (sorry about that .TAP seeking thing in V7.0!).
As usual, the Demo version can be downloaded from:
http://www.dbit.com/demo.html
Jerome Fine
