28 Jul
2020
28 Jul
'20
7:59 a.m.
Hello All,
I've just cycled one of my old systems which in addition to regular duties also ran my
VMS on SIMH system which participated with some of my real VAXen and Alpha systems.
I've built v3.11 of simh and I'm having difficulty with the newer Pcap device and
wondered if someone else knows the silly obvious thing I'm doing wrong.
Setup:
Ubuntu Server 18.xx LTS. 2x NIC's on the system. One's "eth0" (primary)
and a secondary USB one which is obviously called "enx00e04c360059".
Ideally, I'd like to use one NIC for a promiscuous mode Ethernet, the other for
regular scheduled programming. I've built SIMH in the usual fashion and dumped the
binary's symbol tab via nm and the usual suspects from libpcap seem to be statically
linked and present.
I can:
# id
uid=0(root) gid=0(root) groups=0(root)
# /tmp/simh/BIN/vax
VAX simulator V3.11-0
sim> attach xq eth0
Eth: Pcap capable device not found. You may need to run as root
File open error
sim> attach xq enx00e04c360059
File open error
sim> show xq eth
ETH devices:
eth0 udp:sourceport:remotehost:remoteport (Integrated UDP bridge support)
sim>
This seemed to work quite happily in the old O/S combo and with an older simh + pcap.
Can someone please point me in the correct direction?
Thanks in advance.
Regards,
Al Boyanich
Disclaimer
The information in this e-mail is confidential and may contain content that is subject to
copyright and/or is commercial-in-confidence and is intended only for the use of the above
named addressee. Ifyou are not the intended recipient, you are hereby notified that
dissemination, copying or use of the information is strictly prohibited. If you have
received this e-mail in error, please telephone Fujitsu Australia Limited on 02 9776 4555
or by reply e-mail to the sender and delete the document and all copies thereof.
Whereas Fujitsu Australia Limited would not knowingly transmit a virus within an email
communication, it is the receiver's responsibility to scan all communication and any
files attached for computer viruses and other defects. Fujitsu Australia Limited does not
accept liability for any loss or damage (whether direct, indirect, consequential or
economic) however caused, and whether by negligence or otherwise, which may result
directly or indirectly from this communication or any files attached.
If you do not wish to receive commercial and/or marketing email messages from Fujitsu
Australia Limited, please email unsubscribe at au.fujitsu.com.
28 Jul
28 Jul
3:09 p.m.
3.11? That sounds very old.
I don't know if there are formal releases of SIMH any longer. It's on Github.
There's been a lot of work ongoing, it may well be that the trouble you saw has been
fixed. In any case, it's more likely you can get effective help if you run the
current code.
I use the pdp11 emulator with pcap and it works well.
BTW, there's a list for SIMH: simh at trailing-edge.com
paul
On Jul 28, 2020, at 1:59 AM, Boyanich, Alastair
<Alastair.Boyanich at au.fujitsu.com> wrote:
Hello All,
I?ve just cycled one of my old systems which in addition to regular duties also ran my
VMS on SIMH system which participated with some of my real VAXen and Alpha systems. I?ve
built v3.11 of simh ...
3:22 p.m.
It might not be that old. I've not really kept up to date, but as far as
I know/remember, simh now exists in two branches. There is the V4
version, managed by Mark, which is on github, and then Bob have
continued V3 development on his own, which *might* be at 3.11...
Johnny
On 2020-07-28 15:09, Paul Koning wrote:
3.11? ?That sounds very old.
I don't know if there are formal releases of SIMH any longer. ?It's on
Github. ?There's been a lot of work ongoing, it may well be that the
trouble you saw has been fixed. ?In any case, it's more likely you can
get effective help if you run the current code.
I use the pdp11 emulator with pcap and it works well.
BTW, there's a list for SIMH: simh at trailing-edge.com
<mailto:simh at trailing-edge.com>
paul
> On Jul 28, 2020, at 1:59 AM, Boyanich, Alastair
> <Alastair.Boyanich at au.fujitsu.com
> <mailto:Alastair.Boyanich at au.fujitsu.com>> wrote:
>
> Hello All,
> I?ve just cycled one of my old systems which in addition to regular
> duties also ran my VMS on SIMH system which participated with some of
> my real VAXen and Alpha systems. I?ve built v3.11 of simh ?...
--
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
3:29 p.m.
I thought the same re: old version of SIMH, but Bob refers to the downloads on the
trailing-edge.com site as "Classic". His version 3.11 is dated February 2020.
Mark's github is constantly being updated, however.
I've always built SIMH from github and not used the other downloads as I thought
Bob's releases might be getting a bit stale. I noticed some updated networking code
for the VAX network adapters as well as some console access and some funky paper tape
handling in github. I wondered if all that existed in Bob's release as well.
Cheers, Wiz!!
-----Original Message-----
From: owner-hecnet at Update.UU.SE <owner-hecnet at Update.UU.SE> On Behalf Of
Johnny Billquist
Sent: Tuesday, 28 July 2020 11:23 PM
To: hecnet at Update.UU.SE; Boyanich, Alastair <Alastair.Boyanich at
au.fujitsu.com>; Paul Koning <paulkoning at comcast.net>
Subject: Re: [HECnet] SIMH VAX config changes
It might not be that old. I've not really kept up to date, but as far as I
know/remember, simh now exists in two branches. There is the V4 version, managed by Mark,
which is on github, and then Bob have continued V3 development on his own, which *might*
be at 3.11...
Johnny
On 2020-07-28 15:09, Paul Koning wrote:
3.11? ?That sounds very old.
I don't know if there are formal releases of SIMH any longer. ?It's on
Github. ?There's been a lot of work ongoing, it may well be that the
trouble you saw has been fixed. ?In any case, it's more likely you can
get effective help if you run the current code.
I use the pdp11 emulator with pcap and it works well.
BTW, there's a list for SIMH: simh at trailing-edge.com
<mailto:simh at trailing-edge.com>
paul
> On Jul 28, 2020, at 1:59 AM, Boyanich, Alastair
> <Alastair.Boyanich at au.fujitsu.com
> <mailto:Alastair.Boyanich at au.fujitsu.com>> wrote:
>
> Hello All,
> I?ve just cycled one of my old systems which in addition to regular
> duties also ran my VMS on SIMH system which participated with some of
> my real VAXen and Alpha systems. I?ve built v3.11 of simh ?...
--
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
6:01 p.m.
On Tuesday, July 28, 2020 at 6:29 AM, David Moylan wrote:
I thought the same re: old version of SIMH, but Bob
refers to the downloads
on the trailing-edge.com site as "Classic". His version 3.11 is dated February
2020.
Mark's github is constantly being updated, however.
Bob's "Classic" stuff is visible in the "Supnik-Current" branch of
the Github simh repo.
It contains the base simulators that Bob wrote originally (and thus is the primary
maintainer). All changes made to Bob's base simulators either are a consequence of
feedback that inspired changes in the master branch simulators or are changes
he introduces out of the blue (very rare) that are then merged back into the
master branch. Anything which works in a 3.x simulator is guaranteed to work
in the related master branch simulator. The simh base framework (aka SCP)
is functionally the same since around the 3.8 timeframe some 12 years ago.
I've always built SIMH from github and not used
the other downloads as I
thought Bob's releases might be getting a bit stale. I noticed some updated
networking code for the VAX network adapters as well as some console
access and some funky paper tape handling in github. I wondered if all that
existed in Bob's release as well.
The networking code (and XQ and XU device simulators) were written and
maintained by others (Dave Hittner and myself), and are directly maintained
in the master branch and exist essentially unmodified in the Supnik-Current
branch.
If you have network issues or questions, you'll get support and direction
when working with the master branch codebase.
- Mark
-----Original Message-----
From: owner-hecnet at Update.UU.SE <owner-hecnet at Update.UU.SE> On
Behalf Of Johnny Billquist
Sent: Tuesday, 28 July 2020 11:23 PM
To: hecnet at Update.UU.SE; Boyanich, Alastair
<Alastair.Boyanich at au.fujitsu.com>; Paul Koning
<paulkoning at comcast.net>
Subject: Re: [HECnet] SIMH VAX config changes
It might not be that old. I've not really kept up to date, but as far as I
know/remember, simh now exists in two branches. There is the V4 version,
managed by Mark, which is on github, and then Bob have continued V3
development on his own, which *might* be at 3.11...
Johnny
On 2020-07-28 15:09, Paul Koning wrote:
3.11? ?That sounds very old.
I don't know if there are formal releases of SIMH any longer. ?It's on
Github. ?There's been a lot of work ongoing, it may well be that the
trouble you saw has been fixed. ?In any case, it's more likely you can
get effective help if you run the current code.
I use the pdp11 emulator with pcap and it works well.
BTW, there's a list for SIMH: simh at trailing-edge.com
<mailto:simh at trailing-edge.com>
paul
> On Jul 28, 2020, at 1:59 AM, Boyanich, Alastair
> <Alastair.Boyanich at au.fujitsu.com
> <mailto:Alastair.Boyanich at au.fujitsu.com>> wrote:
>
> Hello All,
> I?ve just cycled one of my old systems which in addition to regular
> duties also ran my VMS on SIMH system which participated with some of
> my real VAXen and Alpha systems. I?ve built v3.11 of simh ?...
--
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
3 Aug
3 Aug
3:49 a.m.
Hi Paul,
Thanks. Few emails on it. Tim Sneddon actually piped up with a similar round-up. I
obviously had the wrong impression that the formal releases were the way to go given my
experience as a developer rather than the ?hold my beer and watch this? ..check out from
the trunk. *Chuckle* Okay. Well I?ve tried the trunk and it sort of works. I suspect the
issue now (separate one) is with my hardware. For some reason the dedicated USB Ethernet
adapter drops the odd packet or six..
%ping 10.0.0.100
PING 10.0.0.100 (10.0.0.100) 56(84) bytes of data.
64 bytes from 10.0.0.100: icmp_seq=2 ttl=64 time=14.6 ms
64 bytes from 10.0.0.100: icmp_seq=3 ttl=64 time=18.1 ms
64 bytes from 10.0.0.100: icmp_seq=15 ttl=64 time=16.6 ms
64 bytes from 10.0.0.100: icmp_seq=42 ttl=64 time=13.4 ms
^C
--- 10.0.0.100 ping statistics ---
47 packets transmitted, 4 received, 91% packet loss, time 47010ms
rtt min/avg/max/mdev = 13.470/15.723/18.189/1.815 ms
%
At least ?some? data is flowing. :>
Al.
From: owner-hecnet at Update.UU.SE <owner-hecnet at Update.UU.SE> On Behalf Of Paul
Koning
Sent: Tuesday, 28 July 2020 11:10 PM
To: hecnet at update.uu.se; Boyanich, Alastair <Alastair.Boyanich at
au.fujitsu.com>
Subject: Re: [HECnet] SIMH VAX config changes
3.11? That sounds very old.
I don't know if there are formal releases of SIMH any longer. It's on Github.
There's been a lot of work ongoing, it may well be that the trouble you saw has been
fixed. In any case, it's more likely you can get effective help if you run the
current code.
I use the pdp11 emulator with pcap and it works well.
BTW, there's a list for SIMH: simh at trailing-edge.com<mailto:simh at
trailing-edge.com>
paul
On Jul 28, 2020, at 1:59 AM, Boyanich, Alastair <Alastair.Boyanich at
au.fujitsu.com<mailto:Alastair.Boyanich at au.fujitsu.com>> wrote:
Hello All,
I?ve just cycled one of my old systems which in addition to regular duties also ran my VMS
on SIMH system which participated with some of my real VAXen and Alpha systems. I?ve built
v3.11 of simh ...
Disclaimer
The information in this e-mail is confidential and may contain content that is subject to
copyright and/or is commercial-in-confidence and is intended only for the use of the above
named addressee. Ifyou are not the intended recipient, you are hereby notified that
dissemination, copying or use of the information is strictly prohibited. If you have
received this e-mail in error, please telephone Fujitsu Australia Limited on 02 9776 4555
or by reply e-mail to the sender and delete the document and all copies thereof.
Whereas Fujitsu Australia Limited would not knowingly transmit a virus within an email
communication, it is the receiver?s responsibility to scan all communication and any files
attached for computer viruses and other defects. Fujitsu Australia Limited does not accept
liability for any loss or damage (whether direct, indirect, consequential or economic)
however caused, and whether by negligence or otherwise, which may result directly or
indirectly from this communication or any files attached.
If you do not wish to receive commercial and/or marketing email messages from Fujitsu
Australia Limited, please email unsubscribe at au.fujitsu.com.
1603
days inactive
1609
days old
5 comments
5 participants
participants (5)
-
Alastair.Boyanich＠au.fujitsu.com -
bqt＠softjar.se -
djm＠wiz.net.au -
Mark＠infocomm.com -
paulkoning＠comcast.net