jguillaumes/simh-pdpbsd repository overview

⁠Image contents

This image contains a compiled PDP-11 simulator (from SIMH) and a ready to run BSD 2.11 image. The BSD system is configured with a DZ terminal multiplexor, exposed as port 2323, and with tcp/ip networking.

WARNING This is not an official part of the simh project. I offer this image, and the others based on it, "as is", without no commitment to keep supporting it in the future (as though I will try my best). If you find a bug, please do not report it to the official simh mantainers unless you can reproduce it in a "non containerized" environment. If you suspect the bug is related to the containerization, please open an issue in the specific github project, git://github.com/jguillaumes/dockersimh.

⁠Usage

Create container and initial run:

docker run --name <containerName> -it -p 2323:2323 jguillaumes/simh-pdpbsd

The container will boot straight to BSD:

PDP-11 simulator V4.0-0 Beta        git commit id: 550e3607
Logging to file "console.log"
Disabling RK
Disabling HK
Disabling TM
Listening on port 2323
LPT: creating new file
libpcap version 1.6.2
Eth: opened OS device eth0

73Boot from ra(0,0,0) at 0172150
: 

Just press Return and that prompt, and BSD will begin to boot into single user:

: ra(0,0,0)unix
Boot: bootdev=02400 bootcsr=0172150

2.11 BSD UNIX #7: Thu Jun 8 21:53:04 PDT 1995
    root@:/usr/src/sys/DOKBSD

ra0: Ver 3 mod 3
ra0: RA81  size=891072
attaching qe0 csr 174440
qe0: DEC DEQNA addr 08:00:2b:aa:bb:cc
attaching sl
attaching lo0

phys mem  = 4186112
avail mem = 3730240
user mem  = 307200

May  9 05:46:13 init: configure system

dhv 0 csr 160440 vector 300 attached
lp ? csr 177514 vector 200 skipped:  No autoconfig routines.
ra 0 csr 172150 vector 154 vectorset attached
rl 0 csr 174400 vector 160 attached
tms 0 csr 174500 vector 260 vectorset attached
erase, kill ^U, intr ^C
# 

Now you can issue commands in single user mode, or exit that shell to continue the boot into full multiuser pressing CTRL-D:

# Fast boot ... skipping disk checks
checking quotas: done.
Assuming NETWORKING system ...
add host dokbsd: gateway localhost
add net default: gateway 172.17.0.1
starting system logger
checking for core dump... 
May  9 05:46:32 dokbsd vmunix: ra0: Ver 3 mod 3
May  9 05:46:32 dokbsd vmunix: ra0: RA81  size=891072
preserving editor files
clearing /tmp
standard daemons: update cron accounting.
starting network daemons: inetd rwhod printer.
May  9 05:46:32 dokbsd lpd[79]: unable to get network name for local machine dokbsd
starting local daemons: sendmail.
May  9 05:46:32 dokbsd ntpd[100]: init_ntp: bad drift compensation value
Mon May  9 05:46:32 PDT 2016
May  9 05:46:32 dokbsd init: kernel security level changed from 0 to 1


2.11 BSD UNIX (dokbsd) (console)

login: 

You can now login as root, with no password.

You can also logon using the emulated multiplexor, using TELNET into the exposed 2323 port in the docker machine:

elnet 192.168.99.100 2323
Trying 192.168.99.100...
Connected to dockerhost.
Escape character is '^]'.


Connected to the PDP-11 simulator VH device, line 0

?
 ?
  ?.???BSD?UN?ؠ(c?rl?.????.co???(tt?00??
                                        ??
                                          ?lo?i?:?

For some reason, the terminal line does not configure properly until you enter something. So enter whatever you want and it will fix itself:

????
                                                     Password:
Login incorrect
login: 

⁠Networking

The BSD system has network support compiled in, and the simh configuration attaches the DEQNA simulated devide to eth0 in the container. It is configured as follows:

• IP Address: 172.17.0.102 / 255.255.0.0
• Default route: 172.17.0.1
• Host name: dokbsd
• DNS Server: 10.0.2.3

You must update this setup to fit your configuration. If you are using the default Docker network configuration, the IP address and route will probably be OK. You will definitely have to update the nameserver information. The relevant files you will probably need to edit are:

/etc/hosts
/etc/networks
/etc/netstart
/etc/resolv.conf

Outbound IP access should just work. If you want to enable inbound access (ie, telnet into your PDP-11) you will have to add routing rules to your host OS and probably to your local router.

⁠Copyright notice for SIMH

Copyright (c) 1993-2014, Robert M Supnik

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL ROBERT M SUPNIK BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Except as contained in this notice, the name of Robert M Supnik shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from Robert M Supnik.