More info on that dump:
* Please enter time and date (Default:17-MAR-2013 11:54) [S]:
ACS SY:/BLKS=1024.
CON ONLINE ALL
ELI /LOG/LIM
CLI /INIT=DCL/CTRLC/DPR="<15><12>/$ /"
INS LB:[1,1]RMSRESAB.TSK/RON=YES/PAR=GEN
INS LB:[1,1]RMSLBL.TSK/RON=YES/PAR=GEN
INS LB:[1,1]RMSLBM.TSK/RON=YES/PAR=GEN
INS $QMGCLI
INS $QMGCLI/TASK=...PRI
INS $QMGCLI/TASK=...SUB
QUE /START:QMG
INS $QMGPRT/TASK=PRT.../SLV=NO
QUE LP0:/CR/NM
START/ACCOUNTING
11:54:17 STAT0 -- 73. *ERROR* on scan file open
11:54:17 STAT0 -- 4. FCS I/O error code = 334
file: DU0:[???,???]SYSSCAN.TMP;1
CON ESTAT LP0:
QUE BAP0:/BATCH
QUE BAP0:/AS:BATCH
@ <EOF>
That happened at reboot - maybe something to do with the system accounting (not that I have much of an idea what that is)?
--
Mark Benson
http://DECtec.info
Twitter: @DECtecInfo
HECnet: STAR69::MARK
Online Resource & Mailing List for DEC Enthusiasts.
Mark Benson wrote:
11:37:20 SYSLOG -- 70. *ERROR* On scan file open
11:37:20 SYSLOG -- 4. FCS I/O error code = 334
file: DU0:[???,???]SYSSCAN.TMP;1
Try to boot system, press CTRL/Z at the `Please enter time and date' prompt, and type the following commands:
>CHD 1 6
>PIP SYSSCAN.TMP;*/RM
>INS $VFY
>VFY LB:/LO
>DEL [1,3]*.*;*
>BOO [1,54]
On 14 Mar 2013, at 23:52, Johnny Billquist wrote:
On 2013-03-14 22:46, Mark Benson wrote:
On 14 Mar 2013, at 15:36, blmink wrote:
There's file on trailing-egde:
ftp://ftp.trailing-edge.com/pub/rsxdists/rsx11mplus_4_6_bl87_dsk.zip
It contains rsx11mplus_4_6_bl87.dsk disk image.
Incidentally, is it possible to SYSGEN a fresh system to a clean disk image from this RSX-11MPlus 4.6 image?
I ask because I'm fed up with being stuck on 4.2 and having to tell my PDP-11 sims it's 1985 :D I'd much prefer a Y2K compliant version of RSX-11M Plus, which 4.6 is, but would like it SYSGEN'd to my emulated system on a fresh drive if possible.
As far as I know (I haven't looked thoroughly), it is a complete system. So you should be able to do a SYSGEN just fine.
Has anyone using the above 4.6 system had any issues with the following. I periodically get the message on the console:
11:37:20 SYSLOG -- 70. *ERROR* On scan file open
11:37:20 SYSLOG -- 4. FCS I/O error code = 334
file: DU0:[???,???]SYSSCAN.TMP;1
It repeats dead-on 5 minutes according to the timestamps, which suggests it;'s something periodic the system is doing, and is nothing to do with the SYSGEN that's running at the moment.
It seems to be having a problem accessing some kind of temporary file? Do I need to worry about it or can I safely ignore it? IIRC it happened to me when I used 4.2 at some point too, but on totally different SimH emulation setups. Once my SYSGEN has finished I'll try creating a new user and logging in there to see if it still happens.
--
Mark Benson
http://DECtec.info
Twitter: @DECtecInfo
HECnet: STAR69::MARK
Online Resource & Mailing List for DEC Enthusiasts.
On 17 Mar 2013, at 00:23, "Dave McGuire" <mcguire at neurotica.com> wrote:
On 03/17/2013 12:06 AM, Cory Smelosky wrote:
Indeed it is. I hope OpenSXCE gets off the ground in a meaningful
way.
It runs great. I talk with the guy (Martin) every now and then.
I believe he's the kind of guy who is motivated by people actually
using his stuff. I say RUN it. (it runs great!) And tell him about
it. Thank him for it. Then he'll continue to make it happen.
I did that a little while ago and never got a response. I believe I
was polite and I know I definitely thanked him. I was certainly not
insulting him. I would run it if I could get zones to work at all.
That's the limiting factor for running OpenSXCE. Along with my
inability to get more than the one drive working to help with
staging. ;)
Remember he has only sporadic network access.
Ahhh. Right. I keep forgetting about that.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 03/17/2013 12:06 AM, Cory Smelosky wrote:
Indeed it is. I hope OpenSXCE gets off the ground in a meaningful
way.
It runs great. I talk with the guy (Martin) every now and then.
I believe he's the kind of guy who is motivated by people actually
using his stuff. I say RUN it. (it runs great!) And tell him about
it. Thank him for it. Then he'll continue to make it happen.
I did that a little while ago and never got a response. I believe I
was polite and I know I definitely thanked him. I was certainly not
insulting him. I would run it if I could get zones to work at all.
That's the limiting factor for running OpenSXCE. Along with my
inability to get more than the one drive working to help with
staging. ;)
Remember he has only sporadic network access.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 16 Mar 2013, at 23:46, "Dave McGuire" <mcguire at neurotica.com> wrote:
On 03/15/2013 07:36 PM, Brian Hechinger wrote:
Yes! Now to get the NICs working so I can test simh entirely.;)
What do you need NICs for simh? What are you running?
Solaris 10 zone. klh10 and some of my VMs need dedicated NICs in
order to function properly with DECnet.
-brian
Get 11 if you can. CrossBow makes this SOOOOOOOOOOOO much easier. :)
I'm using a SPARC. Solaris 11 dropped support for UltraSPARC III.
That SUCKS! Ok, carry on as you were. :)
It really does suck. :( The sun fire V480 is a great piece of hardware.
Indeed it is. I hope OpenSXCE gets off the ground in a meaningful way.
It runs great. I talk with the guy (Martin) every now and then. I
believe he's the kind of guy who is motivated by people actually using
his stuff. I say RUN it. (it runs great!) And tell him about it. Thank
him for it. Then he'll continue to make it happen.
I did that a little while ago and never got a response. I believe I was polite and I know I definitely thanked him. I was certainly not insulting him. I would run it if I could get zones to work at all. That's the limiting factor for running OpenSXCE. Along with my inability to get more than the one drive working to help with staging. ;)
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 03/15/2013 07:36 PM, Brian Hechinger wrote:
Yes! Now to get the NICs working so I can test simh entirely.;)
What do you need NICs for simh? What are you running?
Solaris 10 zone. klh10 and some of my VMs need dedicated NICs in
order to function properly with DECnet.
-brian
Get 11 if you can. CrossBow makes this SOOOOOOOOOOOO much easier. :)
I'm using a SPARC. Solaris 11 dropped support for UltraSPARC III.
That SUCKS! Ok, carry on as you were. :)
It really does suck. :( The sun fire V480 is a great piece of hardware.
Indeed it is. I hope OpenSXCE gets off the ground in a meaningful way.
It runs great. I talk with the guy (Martin) every now and then. I
believe he's the kind of guy who is motivated by people actually using
his stuff. I say RUN it. (it runs great!) And tell him about it. Thank
him for it. Then he'll continue to make it happen.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 15 Mar 2013, at 19:41, "Brian Hechinger" <wonko at 4amlunch.net> wrote:
On 3/15/2013 7:35 PM, Mark Pizzolato - Info Comm wrote:
On Friday, March 15, 2013 at 4:07 PM, Brian Hechinger wrote:
On 3/15/2013 7:00 PM, Cory Smelosky wrote:
Yes! Now to get the NICs working so I can test simh entirely.;)
What do you need NICs for simh? What are you running?
Historically, if you want your host system to be able to communicate with the guest simh system on most *nix platforms, the simplest way to get that working is to dedicate a NIC to the simh instance and connect it to the same LAN as your host system.
Alternative approaches which were always more complex and not available on all *nix platforms involved the use of tap devices and internal bridging configured on the host system. Doing this has completely different recipes on each platform and possibly on different versions of the same platform. With versions of simh 3.9 and beyond, Windows system can simply share the host systems NIC and also communicate directly with it. Some *nix platforms have support for libvdeplug. These platforms can also be configured to avoid the addition of a dedicated NIC for the simh instance. The 0readme_ethernet.txt file in the simh source distribution describes the known ways which have been used to address this issue on various platforms.
I ask because Solaris 11 (and the Illumos based stuff like OpenIndiana) have support for the new CrossBow network virtualisation.
CrossBow is awesome. I wish it had been back ported.
You create "vnics" and they all share a physical nic in just the way simh needs. It's what I'll be doing.
For example, on my machine I'll be doing the following (once I get rebooted and IDLE works):
dladm create-vnic -l bge1 -v 152 simh1
dladm create-vnic -l bge1 -v 152 simh2
That will create two nics named simh1 and simh2 that simh can use. They will both use and share the physical interface bge1 along with some other stuff. The -v is the VLAN ID. In my setup this interface is a VLAN trunk into the switch and VLAN 152 is my DECnet VLAN.
Ahhh. That's not as fun as using quad-PHY NICs though. ;)
-brian
On 3/15/2013 7:35 PM, Mark Pizzolato - Info Comm wrote:
On Friday, March 15, 2013 at 4:07 PM, Brian Hechinger wrote:
On 3/15/2013 7:00 PM, Cory Smelosky wrote:
Yes! Now to get the NICs working so I can test simh entirely.;)
What do you need NICs for simh? What are you running?
Historically, if you want your host system to be able to communicate with the guest simh system on most *nix platforms, the simplest way to get that working is to dedicate a NIC to the simh instance and connect it to the same LAN as your host system.
Alternative approaches which were always more complex and not available on all *nix platforms involved the use of tap devices and internal bridging configured on the host system. Doing this has completely different recipes on each platform and possibly on different versions of the same platform. With versions of simh 3.9 and beyond, Windows system can simply share the host systems NIC and also communicate directly with it. Some *nix platforms have support for libvdeplug. These platforms can also be configured to avoid the addition of a dedicated NIC for the simh instance. The 0readme_ethernet.txt file in the simh source distribution describes the known ways which have been used to address this issue on various platforms.
I ask because Solaris 11 (and the Illumos based stuff like OpenIndiana) have support for the new CrossBow network virtualization.
You create "vnics" and they all share a physical nic in just the way simh needs. It's what I'll be doing.
For example, on my machine I'll be doing the following (once I get rebooted and IDLE works):
dladm create-vnic -l bge1 -v 152 simh1
dladm create-vnic -l bge1 -v 152 simh2
That will create two nics named simh1 and simh2 that simh can use. They will both use and share the physical interface bge1 along with some other stuff. The -v is the VLAN ID. In my setup this interface is a VLAN trunk into the switch and VLAN 152 is my DECnet VLAN.
-brian
On 15 Mar 2013, at 19:36, "Brian Hechinger" <wonko at 4amlunch.net> wrote:
On 3/15/2013 7:34 PM, Cory Smelosky wrote:
On 15 Mar 2013, at 19:32, "Brian Hechinger" <wonko at 4amlunch.net> wrote:
On 3/15/2013 7:30 PM, Cory Smelosky wrote:
On 15 Mar 2013, at 19:23, "Brian Hechinger" <wonko at 4amlunch.net> wrote:
On 3/15/2013 7:10 PM, Cory Smelosky wrote:
On 15 Mar 2013, at 19:07, "Brian Hechinger" <wonko at 4amlunch.net> wrote:
On 3/15/2013 7:00 PM, Cory Smelosky wrote:
Yes! Now to get the NICs working so I can test simh entirely.;)
What do you need NICs for simh? What are you running?
Solaris 10 zone. klh10 and some of my VMs need dedicated NICs in order to function properly with DECnet.
-brian
Get 11 if you can. CrossBow makes this SOOOOOOOOOOOO much easier. :)
I'm using a SPARC. Solaris 11 dropped support for UltraSPARC III.
That SUCKS! Ok, carry on as you were. :)
It really does suck. :( The sun fire V480 is a great piece of hardware.
Indeed it is. I hope OpenSXCE gets off the ground in a meaningful way.
Yeah right now it lacks support for creating zones due to the different package management system.
-brian
