New download link for the PiDP-11 software

1,315 views
Skip to first unread message

oscarv

unread,
Jun 20, 2022, 11:04:22 AM6/20/22
to [PiDP-11]
Hi,

Many thanks to Terry for hosting these files for so many years!
But here are the new download links now his server is offline:

The Building instructions web page and the manual have been updated accordingly.

Please do let me know if you have any issues with these download links!

Kind regards,

Oscar.

Heinz-Bernd Eggenstein

unread,
Jun 20, 2022, 1:36:29 PM6/20/22
to [PiDP-11]
Hi!

I think it would be much better to use https links (instead of http) because these days, some (most) browsers will complain or even outright reject any downloads via http.

Cheers
HB

Adam Thornton

unread,
Jun 20, 2022, 1:44:41 PM6/20/22
to oscarv, [PiDP-11]
Some discoverability, so you could go to pidp11.net and then find your way to the files without having to know the link, would also be nice.  I also think a redirect from HTTP to HTTPS would be nice.

--
You received this message because you are subscribed to the Google Groups "[PiDP-11]" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pidp-11+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pidp-11/9c5a4054-d874-450d-966c-01cfb2bb0073n%40googlegroups.com.

Heinz-Bernd Eggenstein

unread,
Jun 20, 2022, 2:17:13 PM6/20/22
to [PiDP-11]
The links will already work with https://... so a redirect is in place, you just need to change the links on the website.

HBE

Tom Lake

unread,
Jun 20, 2022, 9:36:47 PM6/20/22
to [PiDP-11]
When I try to do the unpack from the instructions in the manual I get this:

$ sudo tar -xvf pidp11.tar.gz

tar: This does not look like a tar archive
tar: Skipping to next header
tar: Exiting with failure status due to previous errors

Clem Cole

unread,
Jun 20, 2022, 9:38:47 PM6/20/22
to Tom Lake, [PiDP-11]
Add the -z flag to tell it that is gz encrypted 

--
You received this message because you are subscribed to the Google Groups "[PiDP-11]" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pidp-11+u...@googlegroups.com.
--
Sent from a handheld expect more typos than usual

Clem Cole

unread,
Jun 20, 2022, 9:40:34 PM6/20/22
to Tom Lake, [PiDP-11]
s/encrypt/compress/ sorry 

Tom Lake

unread,
Jun 20, 2022, 9:43:16 PM6/20/22
to [PiDP-11]
Here's the wget step. It appears to go OK:

$ sudo wget http://pidp.net/pidp11/pidp11.tar.gz
--2022-06-20 21:33:47--  http://pidp.net/pidp11/pidp11.tar.gz
Resolving pidp.net (pidp.net)... 66.235.200.146
Connecting to pidp.net (pidp.net)|66.235.200.146|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3534521 (3.4M) [application/x-gzip]
Saving to: ‘pidp11.tar.gz’

pidp11.tar.gz                 100%[===============================================>]   3.37M  21.1MB/s    in 0.2s    

2022-06-20 21:33:47 (21.1 MB/s) - ‘pidp11.tar.gz’ saved [3534521/3534521]

Tom Lake

unread,
Jun 20, 2022, 9:47:02 PM6/20/22
to [PiDP-11]
What should the tar command line look like? Sorry, I'm not a Linux person.

Warner Losh

unread,
Jun 20, 2022, 9:48:37 PM6/20/22
to Tom Lake, [PiDP-11]
It would be

tar -xvzf pidp11.tar.gz

Warner 


Tom Lake

unread,
Jun 20, 2022, 9:52:09 PM6/20/22
to [PiDP-11]
Still no go:

$ tar -xvzf pidp11.tar.gz

tar: This does not look like a tar archive
tar: Skipping to next header
tar: Exiting with failure status due to previous errors

Clem Cole

unread,
Jun 20, 2022, 9:54:08 PM6/20/22
to Tom Lake, [PiDP-11]
tar zvfp pidp11.tar.gz

p flag preserves the permission and owner ship

As I said the Carl recently.  Do your self a favor a get a copy of The Unix Programming Environment by Kernighan and Pike.    Read it and the do the exercises.   You can find a pdf of it in the wild.  

Your RPI is a Unix box tgat is hosting everything. You really need to know a little before you will understand the directions even if you want to run a DEC OS under simh.  You are likely to run into a lot of issues if you don’t understand how to use Unix. It will save you much frustration 



Good luck


Clem Cole

unread,
Jun 20, 2022, 9:57:58 PM6/20/22
to Tom Lake, [PiDP-11]
Type: file pipd11.tar.gz

Assuming it says gz compressed file you can run:  gunzip pidp11.tar.gz

Then type: file pidp11.tar

Then tar xvfp pipd11.tar 

Will work


man command is your friend

Message has been deleted

Anton Lavrentiev

unread,
Jun 20, 2022, 10:27:43 PM6/20/22
to Tom Lake, [PiDP-11]
Tim, please try using the "z" option in addition, "tar zxvf filename" (BTW the '-' is optional in the gnu tar, and was not even a thing for the original tar at all)

amp...@gmail.com

unread,
Jun 20, 2022, 10:29:17 PM6/20/22
to Tom Lake, [PiDP-11]

It appears that it was gzip’d twice.

 

amp1@amp1-PE-T410:~/x$ wget http://pidp.net/pidp11/pidp11.tar.gz

--2022-06-20 22:26:34--  http://pidp.net/pidp11/pidp11.tar.gz

Resolving pidp.net (pidp.net)... 66.235.200.146

Connecting to pidp.net (pidp.net)|66.235.200.146|:80... connected.

HTTP request sent, awaiting response... 200 OK

Length: 3534521 (3.4M) [application/x-gzip]

Saving to: ‘pidp11.tar.gz’

 

pidp11.tar.gz       100%[===================>]   3.37M   327KB/s    in 10s

 

2022-06-20 22:26:44 (336 KB/s) - ‘pidp11.tar.gz’ saved [3534521/3534521]

 

amp1@amp1-PE-T410:~/x$ file pidp11.tar.gz

pidp11.tar.gz: gzip compressed data, from Unix, original size modulo 2^32 3547194

amp1@amp1-PE-T410:~/x$ gunzip pidp11.tar.gz

amp1@amp1-PE-T410:~/x$ ls

pidp11.tar

amp1@amp1-PE-T410:~/x$ file pidp11.tar

pidp11.tar: gzip compressed data, last modified: Wed Aug 14 19:01:32 2019, from Unix, original size modulo 2^32 11171840

amp1@amp1-PE-T410:~/x$ mv pidp11.tar pidp11.tar.gz

amp1@amp1-PE-T410:~/x$ gunzip pidp11.tar.gz

amp1@amp1-PE-T410:~/x$ file pidp11.tar

pidp11.tar: POSIX tar archive (GNU)

amp1@amp1-PE-T410:~/x$ tar xvf pidp11.tar

./bin/

./bin/down.sh

./bin/clean.sh

./bin/client11

./bin/server11

./bin/makesys.sh

./bin/test.py

./bin/rebootsimh.sh

./bin/pidp11.sh

./bin/getsel.sh

./bin/scansw

./bin/makeball.sh

./install/

./install/install.sh

./etc/

./etc/pdp.sh

./etc/rc.pidp11

./src/

./src/original_make.sh

./src/00_common/

./src/00_common/getopt2.c

./src/00_common/errno2txt.h

./src/00_common/namevaluelist.h

./src/00_common/namevaluelist.c

./src/00_common/kbhit.c

./src/00_common/radix.c

./src/00_common/mcout.c

./src/00_common/bitcalc.h

./src/00_common/radix.h

./src/00_common/mcout.h

./src/00_common/getopt2.h

./src/00_common/bitcalc.c

./src/00_common/errno2txt.c

./src/00_common/getopt2_example.c

./src/00_common/.project

./src/00_common/inputline.h

./src/00_common/.cproject

./src/00_common/inputline.c

./src/00_common/kbhit.h

./src/11_pidp_server/

./src/11_pidp_server/pidp11/

./src/11_pidp_server/pidp11/main.h

./src/11_pidp_server/pidp11/makefile

./src/11_pidp_server/pidp11/gpiopattern.c

./src/11_pidp_server/pidp11/.settings/

./src/11_pidp_server/pidp11/.settings/language.settings.xml

./src/11_pidp_server/pidp11/.settings/org.eclipse.cdt.core.prefs

./src/11_pidp_server/pidp11/gpio.c

./src/11_pidp_server/pidp11/.project

./src/11_pidp_server/pidp11/bin-rpi/

./src/11_pidp_server/pidp11/bin-rpi/pidp1170_blinkenlightd

./src/11_pidp_server/pidp11/main.c

./src/11_pidp_server/pidp11/.cproject

./src/11_pidp_server/pidp11/gpiopattern.h

./src/11_pidp_server/pidp11/x86/

./src/11_pidp_server/pidp11/x86/pidp1170_blinkenlightd

./src/11_pidp_server/pidp11/gpio.h

./src/11_pidp_server/scanswitch/

./src/11_pidp_server/scanswitch/scansw.c

./src/11_pidp_server/scanswitch/scansw

./src/11_pidp_server/scanswitch/gpio.h

./src/11_pidp_server/scanswitch/Makefile

./src/07.0_blinkenlight_api/

./src/07.0_blinkenlight_api/blinkenlight_panels.h

./src/07.0_blinkenlight_api/historybuffer.h

./src/07.0_blinkenlight_api/blinkenlight_api_server_procs.c

./src/07.0_blinkenlight_api/rpcgen_win32.defect/

./src/07.0_blinkenlight_api/rpcgen_win32.defect/rpcgen.cmd

./src/07.0_blinkenlight_api/historybuffer.c

./src/07.0_blinkenlight_api/blinkenlight_panels.c

./src/07.0_blinkenlight_api/rpc_example2_msg/

./src/07.0_blinkenlight_api/rpc_example2_msg/makefile

./src/07.0_blinkenlight_api/rpc_example2_msg/msgrpc_svc_main.c

./src/07.0_blinkenlight_api/rpc_example2_msg/msgrpc_clnt_main.c

./src/07.0_blinkenlight_api/rpc_example2_msg/msgrpc.x

./src/07.0_blinkenlight_api/rpc_example2_msg/msg_proc.c

./src/07.0_blinkenlight_api/.project

./src/07.0_blinkenlight_api/rpcgen_linux/

./src/07.0_blinkenlight_api/rpcgen_linux/rpc_blinkenlight_api_xdr.c

./src/07.0_blinkenlight_api/rpcgen_linux/makefile

./src/07.0_blinkenlight_api/rpcgen_linux/rpc_blinkenlight_api_svc.c

./src/07.0_blinkenlight_api/rpcgen_linux/rpc_blinkenlight_api.h

./src/07.0_blinkenlight_api/rpcgen_linux/rpc_blinkenlight_api_clnt.c

./src/07.0_blinkenlight_api/rpcgen_linux/rpc_blinkenlight_api.x

./src/07.0_blinkenlight_api/blinkenlight_api_client.c

./src/07.0_blinkenlight_api/rpc_example1_msg/

./src/07.0_blinkenlight_api/rpc_example1_msg/makefile

./src/07.0_blinkenlight_api/rpc_example1_msg/rprintmsg.c

./src/07.0_blinkenlight_api/rpc_example1_msg/msgrpc.x

./src/07.0_blinkenlight_api/rpc_example1_msg/msg_proc.c

./src/07.0_blinkenlight_api/.cproject

./src/07.0_blinkenlight_api/rpc_blinkenlight_api.x

./src/07.0_blinkenlight_api/blinkenlight_api_client.h

./src/07.0_blinkenlight_api/blinkenlight_api_server_procs.h

./src/makeclient.sh

./src/07.1_blinkenlight_server/

./src/07.1_blinkenlight_server/panel_config_grammar/

./src/07.1_blinkenlight_server/panel_config_grammar/makefile

./src/07.1_blinkenlight_server/panel_config_grammar/grammartest.c

./src/07.1_blinkenlight_server/panel_config_grammar/blinkenlight_panel_config.g

./src/07.1_blinkenlight_server/panel_config_grammar/output/

./src/07.1_blinkenlight_server/panel_config_grammar/output/blinkenlight_panel_configParser.h

./src/07.1_blinkenlight_server/panel_config_grammar/output/blinkenlight_panel_configParser.c

./src/07.1_blinkenlight_server/panel_config_grammar/output/blinkenlight_panel_config.tokens

./src/07.1_blinkenlight_server/panel_config_grammar/output/blinkenlight_panel_configLexer.h

./src/07.1_blinkenlight_server/panel_config_grammar/output/blinkenlight_panel_configLexer.c

./src/07.1_blinkenlight_server/panel_config_grammar/.project

./src/07.1_blinkenlight_server/panel_config_grammar/.cproject

./src/07.1_blinkenlight_server/panel_config_grammar/panel_pdp1140_industrial.jpg

./src/07.1_blinkenlight_server/blinkenlightd.init

./src/07.1_blinkenlight_server/main.h

./src/07.1_blinkenlight_server/config.h

./src/07.1_blinkenlight_server/blinkenbus.h

./src/07.1_blinkenlight_server/makefile

./src/07.1_blinkenlight_server/iopattern.h

./src/07.1_blinkenlight_server/remoteinstall.sh

./src/07.1_blinkenlight_server/config.c

./src/07.1_blinkenlight_server/panelsim.c

./src/07.1_blinkenlight_server/.project

./src/07.1_blinkenlight_server/blinkenbus.c

./src/07.1_blinkenlight_server/print.c

./src/07.1_blinkenlight_server/bin-ubuntu-x86/

./src/07.1_blinkenlight_server/bin-ubuntu-x86/run_test.sh

./src/07.1_blinkenlight_server/bin-ubuntu-x86/run_sim.sh

./src/07.1_blinkenlight_server/print.h

./src/07.1_blinkenlight_server/main.c

./src/07.1_blinkenlight_server/.cproject

./src/07.1_blinkenlight_server/iopattern.c

./src/07.1_blinkenlight_server/msvc/

./src/07.1_blinkenlight_server/msvc/blinkenlightd.vcxproj

./src/07.1_blinkenlight_server/msvc/blinkenlightd.sln

./src/07.1_blinkenlight_server/panelsim.h

./src/makeserver.sh

./src/02.3_simh/

./src/02.3_simh/4.x+realcons/

./src/02.3_simh/4.x+realcons/src/

./src/02.3_simh/4.x+realcons/src/0readmeAsynchIO.txt

./src/02.3_simh/4.x+realcons/src/build_mingw_ether.bat

./src/02.3_simh/4.x+realcons/src/sim_card.c

./src/02.3_simh/4.x+realcons/src/sim_ether.h

./src/02.3_simh/4.x+realcons/src/descrip.mms

./src/02.3_simh/4.x+realcons/src/sim_video.c

./src/02.3_simh/4.x+realcons/src/build_mingw_noasync.bat

./src/02.3_simh/4.x+realcons/src/sim_rev.h

./src/02.3_simh/4.x+realcons/src/sim_disk.c

./src/02.3_simh/4.x+realcons/src/sim_fio.h

./src/02.3_simh/4.x+realcons/src/scp_help.h

./src/02.3_simh/4.x+realcons/src/sim_card.h

./src/02.3_simh/4.x+realcons/src/sim_tmxr.h

./src/02.3_simh/4.x+realcons/src/0readme_39.txt

./src/02.3_simh/4.x+realcons/src/0readme_ethernet.txt

./src/02.3_simh/4.x+realcons/src/README.md

./src/02.3_simh/4.x+realcons/src/sim_fio.c

./src/02.3_simh/4.x+realcons/src/sim_sock.h

./src/02.3_simh/4.x+realcons/src/sim_imd.c

./src/02.3_simh/4.x+realcons/src/display/

./src/02.3_simh/4.x+realcons/src/display/vttest.c

./src/02.3_simh/4.x+realcons/src/display/Makefile.340

./src/02.3_simh/4.x+realcons/src/display/type340cmd.h

./src/02.3_simh/4.x+realcons/src/display/vt11.c

./src/02.3_simh/4.x+realcons/src/display/display.h

./src/02.3_simh/4.x+realcons/src/display/carbon.c

./src/02.3_simh/4.x+realcons/src/display/display.c

./src/02.3_simh/4.x+realcons/src/display/README

./src/02.3_simh/4.x+realcons/src/display/vtmacs.h

./src/02.3_simh/4.x+realcons/src/display/smakefile

./src/02.3_simh/4.x+realcons/src/display/type340.h

./src/02.3_simh/4.x+realcons/src/display/ws.h

./src/02.3_simh/4.x+realcons/src/display/build_mingw.bat

./src/02.3_simh/4.x+realcons/src/display/gmakefile

./src/02.3_simh/4.x+realcons/src/display/vt11.h

./src/02.3_simh/4.x+realcons/src/display/win32.c

./src/02.3_simh/4.x+realcons/src/display/type340.c

./src/02.3_simh/4.x+realcons/src/display/test.c

./src/02.3_simh/4.x+realcons/src/display/tst340.c

./src/02.3_simh/4.x+realcons/src/display/x11.c

./src/02.3_simh/4.x+realcons/src/display/sim_ws.c

./src/02.3_simh/4.x+realcons/src/slirp_glue/

./src/02.3_simh/4.x+realcons/src/slirp_glue/sim_slirp.h

./src/02.3_simh/4.x+realcons/src/slirp_glue/README

./src/02.3_simh/4.x+realcons/src/slirp_glue/qemu/

./src/02.3_simh/4.x+realcons/src/slirp_glue/qemu/timer.h

./src/02.3_simh/4.x+realcons/src/slirp_glue/qemu/win32/

./src/02.3_simh/4.x+realcons/src/slirp_glue/qemu/win32/include/

./src/02.3_simh/4.x+realcons/src/slirp_glue/qemu/win32/include/sys/

./src/02.3_simh/4.x+realcons/src/slirp_glue/qemu/win32/include/sys/time.h

./src/02.3_simh/4.x+realcons/src/slirp_glue/qemu/win32/stdbool.h

./src/02.3_simh/4.x+realcons/src/slirp_glue/qemu/win32/inttypes.h

./src/02.3_simh/4.x+realcons/src/slirp_glue/qemu/win32/stdint.h

./src/02.3_simh/4.x+realcons/src/slirp_glue/qemu/error-report.h

./src/02.3_simh/4.x+realcons/src/slirp_glue/qemu/osdep.h

./src/02.3_simh/4.x+realcons/src/slirp_glue/qemu/compiler.h

./src/02.3_simh/4.x+realcons/src/slirp_glue/qemu/main-loop.h

./src/02.3_simh/4.x+realcons/src/slirp_glue/qemu/sysemu/

./src/02.3_simh/4.x+realcons/src/slirp_glue/qemu/sysemu/char.h

./src/02.3_simh/4.x+realcons/src/slirp_glue/qemu/sysemu/os-win32.h

./src/02.3_simh/4.x+realcons/src/slirp_glue/qemu/monitor/

./src/02.3_simh/4.x+realcons/src/slirp_glue/qemu/monitor/monitor.h

./src/02.3_simh/4.x+realcons/src/slirp_glue/qemu/qemu-common.h

./src/02.3_simh/4.x+realcons/src/slirp_glue/qemu/sockets.h

./src/02.3_simh/4.x+realcons/src/slirp_glue/qemu/typedefs.h

./src/02.3_simh/4.x+realcons/src/slirp_glue/qemu/queue.h

./src/02.3_simh/4.x+realcons/src/slirp_glue/qemu/hw/

./src/02.3_simh/4.x+realcons/src/slirp_glue/qemu/hw/hw.h

./src/02.3_simh/4.x+realcons/src/slirp_glue/sim_slirp.c

./src/02.3_simh/4.x+realcons/src/slirp_glue/glib_qemu_stubs.c

./src/02.3_simh/4.x+realcons/src/slirp_glue/glib.h

./src/02.3_simh/4.x+realcons/src/slirp_glue/config-host.h

./src/02.3_simh/4.x+realcons/src/quickmake

./src/02.3_simh/4.x+realcons/src/sim_console.c

./src/02.3_simh/4.x+realcons/src/sim_tape.h

./src/02.3_simh/4.x+realcons/src/build_mingw.bat

./src/02.3_simh/4.x+realcons/src/sim_ether.c

./src/02.3_simh/4.x+realcons/src/PDP11/

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_dup.h

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_cis.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_rf.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_ke.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_lp.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_xq.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_tm.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_xq_bootrom.h

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_pt.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_vt_lunar_rom.h

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_dz.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_ta.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_vh.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_dl.c

./src/02.3_simh/4.x+realcons/src/PDP11/txt2cbn.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_uqssp.h

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_dmc.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_io_lib.h

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_tq.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_dup.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_stddev.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_pclk.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_rx.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_kmc.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_io_lib.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_tu.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_cpumod.h

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_cr_dat.h

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_rh.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_rk.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_cpu.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_dc.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_rs.c

./src/02.3_simh/4.x+realcons/src/PDP11/lunar11/

./src/02.3_simh/4.x+realcons/src/PDP11/lunar11/gtlem.mac

./src/02.3_simh/4.x+realcons/src/PDP11/lunar11/README.txt

./src/02.3_simh/4.x+realcons/src/PDP11/lunar11/lunar.txt

./src/02.3_simh/4.x+realcons/src/PDP11/lunar11/lunar.lda

./src/02.3_simh/4.x+realcons/src/PDP11/lunar11/lunar.dag

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_io.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_ts.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_ry.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_ddcmp.h

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_fp.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_xu.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_cr.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_rc.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_xq.h

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_hk.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_rl.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_rq.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_tc.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_sys.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_mscp.h

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_xu.h

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_vt.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_defs.h

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_td.h

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_vt.c.bak

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_rp.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_cpumod.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_td.c

./src/02.3_simh/4.x+realcons/src/PDP11/pdp11_kg.c

./src/02.3_simh/4.x+realcons/src/scp.h

./src/02.3_simh/4.x+realcons/src/sim_sock.c

./src/02.3_simh/4.x+realcons/src/sim_console.h

./src/02.3_simh/4.x+realcons/src/sim_timer.h

./src/02.3_simh/4.x+realcons/src/sim_defs.h

./src/02.3_simh/4.x+realcons/src/.project

./src/02.3_simh/4.x+realcons/src/sim_frontpanel.h

./src/02.3_simh/4.x+realcons/src/slirp/

./src/02.3_simh/4.x+realcons/src/slirp/mbuf.c

./src/02.3_simh/4.x+realcons/src/slirp/ip_output.c

./src/02.3_simh/4.x+realcons/src/slirp/main.h

./src/02.3_simh/4.x+realcons/src/slirp/ip.h

./src/02.3_simh/4.x+realcons/src/slirp/sbuf.h

./src/02.3_simh/4.x+realcons/src/slirp/udp.h

./src/02.3_simh/4.x+realcons/src/slirp/arp_table.c

./src/02.3_simh/4.x+realcons/src/slirp/tcp_subr.c

./src/02.3_simh/4.x+realcons/src/slirp/tftp.c

./src/02.3_simh/4.x+realcons/src/slirp/if.h

./src/02.3_simh/4.x+realcons/src/slirp/slirp.c

./src/02.3_simh/4.x+realcons/src/slirp/ip_icmp.h

./src/02.3_simh/4.x+realcons/src/slirp/tcp_var.h

./src/02.3_simh/4.x+realcons/src/slirp/README

./src/02.3_simh/4.x+realcons/src/slirp/if.c

./src/02.3_simh/4.x+realcons/src/slirp/tcp_timer.c

./src/02.3_simh/4.x+realcons/src/slirp/mbuf.h

./src/02.3_simh/4.x+realcons/src/slirp/ip_icmp.c

./src/02.3_simh/4.x+realcons/src/slirp/sbuf.c

./src/02.3_simh/4.x+realcons/src/slirp/cksum.c

./src/02.3_simh/4.x+realcons/src/slirp/tcp.h

./src/02.3_simh/4.x+realcons/src/slirp/tftp.h

./src/02.3_simh/4.x+realcons/src/slirp/misc.h

./src/02.3_simh/4.x+realcons/src/slirp/slirp_config.h

./src/02.3_simh/4.x+realcons/src/slirp/socket.c

./src/02.3_simh/4.x+realcons/src/slirp/socket.h

./src/02.3_simh/4.x+realcons/src/slirp/bootp.h

./src/02.3_simh/4.x+realcons/src/slirp/slirp.h

./src/02.3_simh/4.x+realcons/src/slirp/bootp.c

./src/02.3_simh/4.x+realcons/src/slirp/tcp_input.c

./src/02.3_simh/4.x+realcons/src/slirp/tcp_timer.h

./src/02.3_simh/4.x+realcons/src/slirp/Makefile.objs

./src/02.3_simh/4.x+realcons/src/slirp/libslirp.h

./src/02.3_simh/4.x+realcons/src/slirp/udp.c

./src/02.3_simh/4.x+realcons/src/slirp/COPYRIGHT

./src/02.3_simh/4.x+realcons/src/slirp/tcpip.h

./src/02.3_simh/4.x+realcons/src/slirp/misc.c

./src/02.3_simh/4.x+realcons/src/slirp/dnssearch.c

./src/02.3_simh/4.x+realcons/src/slirp/ip_input.c

./src/02.3_simh/4.x+realcons/src/slirp/debug.h

./src/02.3_simh/4.x+realcons/src/slirp/tcp_output.c

./src/02.3_simh/4.x+realcons/src/sim_frontpanel.c

./src/02.3_simh/4.x+realcons/src/helpx

./src/02.3_simh/4.x+realcons/src/sim_imd.h

./src/02.3_simh/4.x+realcons/src/sim_timer.c

./src/02.3_simh/4.x+realcons/src/sim_disk.h

./src/02.3_simh/4.x+realcons/src/.cproject

./src/02.3_simh/4.x+realcons/src/sim_tmxr.c

./src/02.3_simh/4.x+realcons/src/REALCONS/

./src/02.3_simh/4.x+realcons/src/REALCONS/realcons_console_pdp11_40.h

./src/02.3_simh/4.x+realcons/src/REALCONS/realcons_console_pdp11_70.h

./src/02.3_simh/4.x+realcons/src/REALCONS/realcons_console_pdp15.c

./src/02.3_simh/4.x+realcons/src/REALCONS/realcons_pdp10-ki10.txt

./src/02.3_simh/4.x+realcons/src/REALCONS/realcons_pdp10.c

./src/02.3_simh/4.x+realcons/src/REALCONS/realcons_pdp11_70.txt

./src/02.3_simh/4.x+realcons/src/REALCONS/realcons_pdp10_operpanel.c

./src/02.3_simh/4.x+realcons/src/REALCONS/realcons_pdp10_control.c

./src/02.3_simh/4.x+realcons/src/REALCONS/realcons_simh.c

./src/02.3_simh/4.x+realcons/src/REALCONS/realcons.c

./src/02.3_simh/4.x+realcons/src/REALCONS/realcons_simh.h

./src/02.3_simh/4.x+realcons/src/REALCONS/realcons_console_pdp8i.c

./src/02.3_simh/4.x+realcons/src/REALCONS/pdp1170_idle_pattern.txt

./src/02.3_simh/4.x+realcons/src/REALCONS/realcons_pdp10.h

./src/02.3_simh/4.x+realcons/src/REALCONS/realcons_console_pdp11_20.h

./src/02.3_simh/4.x+realcons/src/REALCONS/realcons_console_pdp11_70.c

./src/02.3_simh/4.x+realcons/src/REALCONS/realcons_console_pdp11_20.c

./src/02.3_simh/4.x+realcons/src/REALCONS/realcons_pdp8i.txt

./src/02.3_simh/4.x+realcons/src/REALCONS/realcons_console_pdp8i.h

./src/02.3_simh/4.x+realcons/src/REALCONS/realcons_pdp11_20.txt

./src/02.3_simh/4.x+realcons/src/REALCONS/realcons_pdp11_40.txt

./src/02.3_simh/4.x+realcons/src/REALCONS/realcons_pdp10_maintpanel.c

./src/02.3_simh/4.x+realcons/src/REALCONS/realcons_console_pdp11_40.c

./src/02.3_simh/4.x+realcons/src/REALCONS/realcons_console_pdp15.h

./src/02.3_simh/4.x+realcons/src/REALCONS/realcons_pdp10_control.h

./src/02.3_simh/4.x+realcons/src/REALCONS/realcons.h

./src/02.3_simh/4.x+realcons/src/REALCONS/realcons_pdp15.txt

./src/02.3_simh/4.x+realcons/src/sim_serial.c

./src/02.3_simh/4.x+realcons/src/sim_tape.c

./src/02.3_simh/4.x+realcons/src/sim_serial.h

./src/02.3_simh/4.x+realcons/src/sim_BuildROMs.c

./src/02.3_simh/4.x+realcons/src/sim_video.h

./src/02.3_simh/4.x+realcons/src/scp.c

./src/02.3_simh/4.x+realcons/rpi-build/

./src/02.3_simh/4.x+realcons/rpi-build/libpcap.a

./src/02.3_simh/4.x+realcons/bin-rpi/

./src/02.3_simh/4.x+realcons/bin-rpi/pdp11_realcons

./systems/selections

./systems/idled/

./systems/idled/IDLED_LIST.pdf

./systems/idled/boot.ini

./systems/idled/IDLED_LIST

amp1@amp1-PE-T410:~/x$

amp...@gmail.com

unread,
Jun 20, 2022, 10:35:26 PM6/20/22
to Tom Lake, [PiDP-11]

When I did this:

 

amp1@amp1-PE-T410:~/x$ tar xvf pidp11.tar

 

I should have done this:

 

amp1@amp1-PE-T410:~/x$ tar xvpf pidp11.tar

 

But it DOES seem to have been compressed twice, so you’ll need to uncompress it twice with gunzip.

 

 

Anton Lavrentiev

unread,
Jun 20, 2022, 10:36:09 PM6/20/22
to amp...@gmail.com, Tom Lake, [PiDP-11]
> It appears that it was gzip’d twice.

Oh yeah, it used to be the case, too!... Well "gunzip -c filename |
tar zxvf -" should do the trick then...
> To view this discussion on the web visit https://groups.google.com/d/msgid/pidp-11/023c01d88516%24b14a9760%2413dfc620%24%40gmail.com.

Tom Lake

unread,
Jun 20, 2022, 10:37:37 PM6/20/22
to [PiDP-11]
Success! Thanks. Should the manual be changed for dummies like me?

Warner Losh

unread,
Jun 20, 2022, 10:43:37 PM6/20/22
to Anton Lavrentiev, Tom Lake, [PiDP-11]


On Mon, Jun 20, 2022, 8:27 PM Anton Lavrentiev <anton.la...@gmail.com> wrote:
Tim, please try using the "z" option in addition, "tar zxvf filename" (BTW the '-' is optional in the gnu tar, and was not even a thing for the original tar at all)

If we are going for originality, the tar file would be compressed with 'compress' compiled with 12 bit compression tables (because 13 bits overflowed the original memory limits with the V7 compilers).... and uncompressing in a pipeline :)

Warner

On Mon, Jun 20, 2022, 9:36 PM Tom Lake <toml...@gmail.com> wrote:
When I try to do the unpack from the instructions in the manual I get this:

$ sudo tar -xvf pidp11.tar.gz

tar: This does not look like a tar archive
tar: Skipping to next header
tar: Exiting with failure status due to previous errors

On Monday, June 20, 2022 at 11:04:22 AM UTC-4 oscarv wrote:
Hi,

Many thanks to Terry for hosting these files for so many years!
But here are the new download links now his server is offline:

The Building instructions web page and the manual have been updated accordingly.

Please do let me know if you have any issues with these download links!

Kind regards,

Oscar.

--
You received this message because you are subscribed to the Google Groups "[PiDP-11]" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pidp-11+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pidp-11/d3d625a4-c854-4ac5-a874-c1fc7fe46d4fn%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "[PiDP-11]" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pidp-11+u...@googlegroups.com.

Rob Pike

unread,
Jun 20, 2022, 10:49:08 PM6/20/22
to Clem Cole, Tom Lake, [PiDP-11]
"You can find a pdf of it in the wild."

You can also buy a physical copy. It's still in print, which astonishes me.

-rob

Anton Lavrentiev

unread,
Jun 20, 2022, 10:49:55 PM6/20/22
to Tom Lake, [PiDP-11]
I've seen this double-compression before from the "original" location.
So I think it was some sort of MIME type misconfiguration in the
server that gzipped the file the second time on the fly,
Probably the file was just downloaded to the new location in that
form, as received. Or it's a new "misconfiguration", or a combination
of both LOL
Anyways, if the file is doubly-gzipped on the webserver, the only
thing necessary to fix would be to ungzip it to, and rename the result
to tar.gz again.
No documentation would have to be changed.
> To view this discussion on the web visit https://groups.google.com/d/msgid/pidp-11/0a37f6b4-17a8-43b7-9460-47a6c9216fbfn%40googlegroups.com.

Tom Lake

unread,
Jun 21, 2022, 12:48:51 AM6/21/22
to [PiDP-11]
Sure it would. The docs would have to be changed to include the extra ungzip step and rename step in order for those of us who follow procedures exactly to follow along and have a successful install.

Tom Lake

unread,
Jun 21, 2022, 1:31:18 AM6/21/22
to [PiDP-11]
What I would need in the manual to be able to complete this procedure is something like this: 

3 Unpack it so the software lives in its designated /opt/pidp11/ directory:
               sudo tar -xvf pidp11.tar.gz
    If the above gives an error saying the file isn't a tar, do this instead:
                sudo gunzip pidp11.tar.gz; sudo tar xvpf pidp11.tar

 

Anton Lavrentiev

unread,
Jun 21, 2022, 8:45:13 AM6/21/22
to Tom Lake, [PiDP-11]
The files just need to be re-uploaded to the server without the second round of gzip (as they are now), and then nothing would have to be changed in docs -- that's what I said.

Clem Cole

unread,
Jun 21, 2022, 9:33:28 AM6/21/22
to Rob Pike, Tom Lake, [PiDP-11]
Indeed, mei culpa.  I usually recommend either borrowing a copy from a University/Public library or buying one - ISBN 0-13-937699-2. When I point people at it, I typically offer the search engine note at the end primarily for some folks overseas that often don't have the same library access that we have in the USA, EU, or 'down under.'  [I was using my mobile when I answered it last night and tried to keep typing more limited - I'm bad enough when I have a real keyboard].

But my point stands ... Brian and your books are two of the best ways I know to teach how to use the UNIX tool kit effectively.  You might be amused to know that when I hire "recent college graduates" into the team, I make sure new copies of three books are on their desks when they arrive:  UPE, and the latest editions of Steven's APUE, and his networking book.

Tom Lake

unread,
Jun 22, 2022, 10:33:51 PM6/22/22
to [PiDP-11]
You're right. I misread your post. Since the files have been changed, no doc update is necessary.

oscarv

unread,
Jun 23, 2022, 2:55:27 PM6/23/22
to [PiDP-11]
Ouch - I caused some suffering here!

Apparently my hosting service Bluehost rezips zipped files when you download them, causing the problem discussed here when you use tar.
The solution is to use gzip to unzip the downloaded .tar.gz files first, and only then unleash tar itself.

The manual and web site have been updated accordingly.

And apologies for the misery this caused. Thing is, if you open the archives through a GUI, there is no problem. But tar on the command line *does* object. Wonderful.

Kind regards,

Oscar.


Brian Denley

unread,
Jun 23, 2022, 10:24:24 PM6/23/22
to oscarv, [PiDP-11]
Oscar et Al:
I am about to download the pidp-11 files to my pdp-11 / pi.  Can I still follow the instructions on the website?  All this tar, etc talk s making me nervous.

Thanks
Brian

Brian Denley
KB1VBF
Sent from my iPad

On Jun 23, 2022, at 2:55 PM, oscarv <vermeul...@gmail.com> wrote:


--
You received this message because you are subscribed to the Google Groups "[PiDP-11]" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pidp-11+u...@googlegroups.com.

Anton Lavrentiev

unread,
Jun 23, 2022, 10:53:44 PM6/23/22
to Brian Denley, oscarv, [PiDP-11]
Brian, there's nothing to be nervous about, it's either be two gunzip
plus untar or one gunzip plus untar... GZIP and TAR formats are quite
resilient, so it's safe to experiment, and you won't get something
unpacked if it wasn't in the expected form, that is there's no risk to
get garbage contents, in the end... Just saying
> To view this discussion on the web visit https://groups.google.com/d/msgid/pidp-11/2E1DEA6B-8C50-44CA-93F9-430ED150DCB3%40comcast.net.

terry-...@glaver.org

unread,
Jun 24, 2022, 1:58:53 AM6/24/22
to [PiDP-11]
On Monday, June 20, 2022 at 11:04:22 AM UTC-4 oscarv wrote:
Hi,

Many thanks to Terry for hosting these files for so many years!
But here are the new download links now his server is offline:

It is? News to me. There was some downtime while it was moved, and some subsequently when a power failure lasted for longer than the 4-hour UPS runtime, but it has been up and running at the new site. I never got any email about issues accessing it...

But anyway, do you want me to add a pointer or redirect to the new server? I'm hesitant to do so at this point because https://pidp.net is a placeholder and https://pidp.net/pidp11 returns 403 Forbidden, so people need to know the exact filenames.

Clem Cole

unread,
Jun 24, 2022, 9:40:41 AM6/24/22
to Brian Denley, oscarv, [PiDP-11]
The Unix file(1) program is your friend here.  type: file some_file and it will try to identify the format that the file is stored (see: man file for details).   Here is what I just typed on my mac.  My typing is in BLUE and the response in GREEN.

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 3455k  100 3455k    0     0  5610k      0 --:--:-- --:--:-- --:--:-- 5673k
% curl -O http://pidp.net/pidp11/systems.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  111M  100  111M    0     0  37.1M      0  0:00:03  0:00:03 --:--:-- 37.2M
% curl -O http://pidp.net/pidp11/PiDP-11_Manual.odt
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 6842k  100 6842k    0     0  10.3M      0 --:--:-- --:--:-- --:--:-- 10.5M
% file pi*gz system* PiDP-11_Manual.odt
pidp11.tar.gz:                       gzip compressed data, from Unix, original size modulo 2^32 11171840
systems.tar.gz:                      gzip compressed data, from Unix, original size modulo 2^32 120790386
PiDP-11_Manual.odt:                  OpenDocument Text
% sha256sum pi*gz system* PiDP-11_Manual.odt
ab1984d5b772ed582c336b45d916f7d4f2c5e8a8ba23b9a0287009def4413b62  pidp11.tar.gz
6531b7a3b06bd146ee242360b7cadcc5bdaea0927e33abf829d0562b3bcaf085  systems.tar.gz
60e1dd63078d464add87d2fce7d8115c9f1f51057631dab39cd9ce41ec78a368  PiDP-11_Manual.odt 
% gunzip pi*gz ; gunzip system*
% file pidp11* system*

pidp11.tar:  POSIX tar archive (GNU)
systems.tar: gzip compressed data, last modified: Tue Oct  8 12:43:46 2019, from Unix, original size modulo 2^32 1900492800
% sha256sum pidp11* system*
2c366452182fa447bdb35323bb245ca20c8eff434625294fa899eeac70aa917b  pidp11.tar
4aa771af051d32a50e7193339aa5e04ed33606b6a7700a9a77c03faf87184b14  systems.tar
% mv systems.tar systems.tar.gz
% gunzip systems.tar.gz
% file systems.tar ; sha256sum systems.tar
systems.tar: POSIX tar archive (GNU)
2d208110699937da9039c35d3a5761e0bfe55049468373d69a1a3bd56bd472d5  systems.tar



On Thu, Jun 23, 2022 at 10:24 PM Brian Denley <b.de...@comcast.net> wrote:

Jonathan Morton

unread,
Jun 24, 2022, 6:06:50 PM6/24/22
to Clem Cole, Brian Denley, oscarv, [PiDP-11]
> On 24 Jun, 2022, at 4:40 pm, Clem Cole <cl...@ccc.com> wrote:
>
> The Unix file(1) program is your friend here. type: file some_file and it will try to identify the format that the file is stored (see: man file for details).

Another couple of useful tricks:

1: Use "file -z <filename>" to make it look inside one layer of compression. This identifies pidp11.tar.gz as a TAR archive that is gzipped, but systems.tar.gz as a gzip compressed file that is itself gzipped.

2: Tar has syntactic sugar to handle a single layer of gzip compression (just add the z flag), but to handle two layers without involving temporary files: "zcat systems.tar.gz | gunzip | tar xv". Zcat reads a gzipped file and decompresses it to stdout; gunzip with no arguments decompresses stdin to stdout; tar without the f flag reads an uncompressed archive on stdin.

- Jonathan Morton

Edward Tottenham

unread,
Jun 25, 2022, 6:19:39 AM6/25/22
to pid...@googlegroups.com

If he was nervous before, I'm not sure that will calm him.

In a world where people are used to rt-click .. download .. double-click installer, being told that you should read a book about The Unix Programming Environment in order to install a program is pretty frightening. Just the title is scary, they want to use the computer, not program it.

To somebody who just wants to relive the PDP 11 experience of a DEC OS it's a lot to have to take in.

For those that want simplicity, it would be nice if somewhere there was a downloadeble SDCard image with everything pre-installed. Just burn it onto a microSD Card and you're ready to go.

Ed

Tom Lake

unread,
Jun 25, 2022, 6:52:16 AM6/25/22
to [PiDP-11]

You got that right! All I want to do is run BASIC/2 and BASIC/2 Plus under RSTS/E, not learn UNIX (Linux?) Fortunately, I was able to create a RSTS/E 10.1 disk and log into it from eight serial terminals at a time.
It took a long time to get there, though. There are a lot of people who'd appreciate a plug-and-play solution.

Clem Cole

unread,
Jun 25, 2022, 11:21:20 AM6/25/22
to Edward Tottenham, pid...@googlegroups.com
On Sat, Jun 25, 2022 at 6:19 AM Edward Tottenham <edw...@tottenham.name> wrote:

If he was nervous before, I'm not sure that will calm him.

In a world where people are used to rt-click .. download .. double-click installer, being told that you should read a book about The Unix Programming Environment in order to install a program is pretty frightening.

Sure - although, that is a pretty sad statement.

What you are describing is what I refer to as 'social compliance.' I do 'get it.'  At my $ day job, in fact, I am the leading voice that installers for SW need to match the target system.  That means the Windows Installer for MSFT, macOS Installer for Apple, rpm for Linux, and if like in the old days you used the VMS installer for VMS or setld(1) for Ultrix.

 

Just the title is scary, they want to use the computer, not program it.

Except that Programmers Designed UNIX for Programmers.  And while the book may sound a tad off-putting, if you look at the first few things Rob and Brian do is to remind the reader that the book is about >>using<< UNIX and how to be effective (not quite so scared to use your term).  And to be able to use UNIX, the reader/user is helped if they think a bit more like a programmer.[1]

 

To somebody who just wants to relive the PDP 11 experience of a DEC OS it's a lot to have to take in.

The problem is that you are failing to accept that the kit is using Linux as a host,  if you want to have a seamless experience, you (the builder and user of the kit) need to know a bit more about the environment -which >>is< precisely what Rob and Brian are telling you in their book.

For those that want simplicity, it would be nice if somewhere there was a downloadeble SDCard image with everything pre-installed. Just burn it onto a microSD Card and you're ready to go.

But it would not be the same thing.  It would be a different kit.

Oscar did a fine job, but he used a Unix system to support his front panel and supply the emulated HW.    The point is that PiDP-8/11 today (and maybe a PiDP-10 someday) are RPi systems running a flavor of Unix called Raspian, hosting the UNIX simh program to emulate an 8 or 11, depending.

I understand your saying -- "Yeah but I'm a RSTS/RSX/RT-11 person.  Why do I need to use this UNIX stuff?"  The answer is that that kit uses UNIX to supply the functionality that your desired system will sit on top.  And that requires that you learn a bit about the host environment if you want to use the device.

The reality is the problems people are asking about in this mailing list tend to get into are based on Oscar's design choice to use simh as his emulator, having simh be hosted on an RPi; along with issues associated with the fact that it's an RPi running Raspian/Linux.   So to use Oscar's emulator, a user/builder is quite likely to need to learn about how simh is being hosted and what requirements it is putting on the RPi before you can consider the emulated system. 

This is why I tell >>everyone<< ensure that the RPi is working properly and is talking to things like your network, USB serial devices, emulated disk and tape files, and the like >>before<< you try running the emulated system.   Walk before you try to run.

If you want to make a different kit that works differently and removes the RPi, UNIX, and simh, I think that's a fine idea ... and ... I bet you might have a group of people that love it. Please feel free to do it!!!

The point is that Oscar's kit >>is<< using a socially compliant installation → What the kit provides, maps well to the target. 

So, I ask you to please not complain that the world is different and that you desire the kit to come into your world because that is your world because you and a set of users find it easy.   It's not this one UNIX is the reality of building and using this device.  People like me have tried to explain how to come into the target UNIX provides and try to help unfamiliar people have fewer issues. One excellent way - is do your homework, read UPE and do the exercises offered up on your RPi before you try to build the kit.   I note that Oscar does warn the purchaser that these are 'expert kits.'    So I do not think you should be unhappy if the reality of what you get is different than what you expected.

Note that I can see the value of a small warning in the key of  Knowledge and use of traditional UNIX systems and the Raspian Linux implementation of the same, in particular, is often required to build and successfully use this specific implementation of the kit.  Specific knowledge may be needed if the user wants to try to use the PiDP-11 to talk to traditional DEC-style peripherals such as terminals, printers, and the like.  Attaching them can and has been made to work by many users.  Some of the information is here on the site, but the details/documentation on how to do the same.  While available, they will take reading and learning by the user of the kit as each of these installations can be a little different and thus specific 'Ikea-like' recipes that are difficult, if not impossible.

Clem

1] FWIW:  And UNIX as a system and basic IP for putting together OS 'won' over all the other systems developed before and after.   The core ideas are used by all major systems (including Windows) these days.  Frankly, the point-in-click / GUI nature of Winders (and macOS) has been removed/hidden a great deal of reality of what the OS is actually doing, but if that is your target that is fine.


Edward Tottenham

unread,
Jun 26, 2022, 3:54:42 AM6/26/22
to Clem Cole, pid...@googlegroups.com

Wow, a much more aggressive response than I was expecting. Sorry, in no way was my post meant to have been an attack on Oscar's superb work, nor on Linux.

I'm not complaining that "the world is different and that I desire the kit to come into my world" I've been a Unix user since the 1990s, developing SCADA software, first with with System V and then with Linux. My day job is now writing software for embedded Linux.

I had absolutely no problems setting up the kit. It works just fine for me. As a Linux user, I merely suggested that it might just be possible to make things easier for non-Linux people.

I installed the PiDP 11 on my Raspberry Pi by simply copying the commands that Oscar gave on his web-site it worked first time and, after a year of pretty frequent use, the only Linux command that I have ever needed to use is "shutdown -h now". Other than that, simh is run automatically and I never need to see the command line until the final "exit" from simh. The processor is effectively running an embedded system and could be virtually any OS.

Kudos to Oscar for producing something so easy to use. I would imagine that the vast majority of people who use the PiDP 11 have the same experience. Even those who are non Linux users.

In this case, someone was trying to get his serial lines working with a USB adapter. With help from the people in this group, he has got it working. Now he will, hopefully, be in a similar situation in that he will never need to type another Linux command on the Raspberry Pi inside the PiDP 11.

So, my recommendation to him would have been to do exactly what he did; go and ask the group how to get things working, rather than get a 350+ page book in order to understand the very limited set of commands that he needed in order to get it working. With the help of people in the group, everything works and, other than to close the system down, he will, hopefully, never have to type another Linux command again.

I'm not sure what you mean when you say that the SDCard image wouldn't be the same kit. What I suggested was an SDCard Image with the same Rasbian distro and the PiDP 11 software already  installed on it. Just use Balena Etcher (or your preferred program) to write it to the SDCard and put it in your RPi; it's how we distribute our product at work.  Is it not the same kit because I wouldn't have typed the dozen or so commands to install it?

My home audio system is based on a Raspberry Pi running the SqueezePlay Server. An SDCard image downloaded from Max2Play with Raspbian and their SqueezePlay server and player preinstalled. I've been running it for over 5 years and never had to type a Linux command on it.

I have a set of Raspberry Pi Zeros monitoring temperature and humidity iinside the house and outside, for a while I even had a Raspberry Pi with a Relay Hat using the data from those sensors to control my central heating. All set up with virtually no need to know Linux at all, just download a script which then downloads and installs all the packages needed, sets up the database, etc..

The cheap Raspberry Pi has become a commodity. Software can be written such that it can be used by people with no knowledge of Linux. My phone is Linux (well Android which is underpinned by a modified Linux Kernel and other open-source software). My TV runs Linux, my sattelite decoder runs Linux. Linux doesn't have to be difficult to use, or run from a set of arcane commands.

All I was suggesting was that things could be made even more easy for those who don't want to have to learn a lot of commands that they will use just once and never need again.

Ed

Carl Marbach

unread,
Jun 26, 2022, 8:00:33 AM6/26/22
to [PiDP-11]
Ed, You are NOT alone. 

What is the purpose each of us sought when buying/building this wonderful kit. 
I started on DEC computers (a PDP-6,  precursor to the PDP-10) in 1966. I the early 70's I installed PDP-11s and wrote software for several companies. In the 80's and 90' s
I was the publisher of the DEC Professional magazine and a RSTS/E expert consulting with The White House, The Alyeska Pipeline and Billy Graham to mention a few.
My purpose was to have a functioning PDP-11/70 running RSTS/E on a VT style terminal. I get a smile on my face every time I see the  null job running in blinking lights
and I show people what computing and data processing used to look like on my attached (serial - thanks for the help) terminal.

I love building things (I'm adding the PDP-8I kit) and fooling around in RSTS/E. Unix is just the environment and NOT my purpose.

As one of our forum said, "UNIX is your problem." Then he helped me thorough getting the VT-420 serial terminal working. THANKS.

(Smilin') Carl
Reply all
Reply to author
Forward
0 new messages