PiDP-8/I SoftwareCheck-in [1f0cad3572]
Not logged in

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Updated the discussion of systemd in the top-level README.md file: it was written in terms of the pre-release trunk implementation. We should have made similar changes shortly before release, but overlooked it.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256:1f0cad35728cc6bc28b64fb828da8e139a21643639838f66b90cf2f7f2b1e1ab
User & Date: tangent 2019-05-11 16:25:16
Context
2019-05-11
20:18
Fix for Cygwin "which" in bin/pidp8i: unlike typical implementations, it gripes on stderr when it can't find a match in the PATH. Sending stderr to /dev/null. check-in: 15389943a9 user: tangent tags: trunk
16:25
Updated the discussion of systemd in the top-level README.md file: it was written in terms of the pre-release trunk implementation. We should have made similar changes shortly before release, but overlooked it. check-in: 1f0cad3572 user: tangent tags: trunk
15:33
URL update check-in: 89e22f5975 user: tangent tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to README.md.

51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
...
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
...
865
866
867
868
869
870
871
872
873
874
875

876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
[os]: https://tangentsoft.com/pidp8i/wiki?name=OS+Compatibility


<a id="unpacking"></a>
## Getting the Software onto Your Pi

If you're reading this file within an unpacked distribution of the
PiDP-8/I software, you should skip this section, because you have
already achieved its aim.

If you are reading this [online][this] and have not yet downloaded and
unpacked the software source code onto your Pi, this section will get
you going.

[this]: https://tangentsoft.com/pidp8i/doc/trunk/README.md
................................................................................

In late 2017 [several of us][aut] created the `mkos8` tool, which was
replaced during 2018 by Bill Cattey with the `os8-run` interpreter
and its stock scripts. The `--*-os8-*` options documented above get
passed into `os8-run` during the PiDP-8/I software build process,
which controls how it generates the `v3d*.rk05` RK05 disk image files.

This set of disk images entirely replaces the old `os8.rk05` disk
image, in that all features of the old disk image are still available,
though not necessarily in the default configuration. In some cases,
features pesent on the old `os8.rk05` disk are now left out or disabled
by default, and in other cases we have changed the behavior of features
from the way they used to be on the old disk. Mostly, though, the
new disk images are simply more functional than the old ones.

If you wish to know the full details of how these disk images are
created, see the documentation for [`os8-run`][ori] and that for
[`class simh`][cs].

The remainder of this section describes some aspects of these disk
images which are not clear from the descriptions of the `--*-os8-*`
................................................................................
keys if they are missing on boot, so you need to do this once by hand:

    $ sudo dpkg-reconfigure openssh-server

You should be able to log in via SSH immediately after that command
completes.

We used to do this automatically in releases v2017.12.22 and before,
but that was when we started the `pidp8i` service as root, which we no
longer do. Consequently, the `pidp8i` service no longer has permission
to generate your OS's SSH keys, so you must do it interactively with

`sudo` permissions.


<a id="systemd" name="unit"></a>
## The systemd Unit File

The PiDP-8/I software version 2017.12.22 used an [old-style System V
init script][svinit] to start the PiDP-8/I service, as did all prior
releases, including Oscar Vermeulen's final stable release.

As of 2018.02.22, we have now switched to a [systemd][systemd]
unit file, since we normally install on Raspbian, which has been
systemd-based for years. We've wanted to do this for some time, but
some changes in the way systemd handles SysV init script compatibility
in Raspbian Stretch forced the issue.

One of the features systemd gives us is the ability to set the unit
to run as user-level service rather than as a system-wide service,
which means you no longer need the `sudo` prefix on commands to start,
stop, restart, and query the service. The only time you now need root
privileges is when installing the software. After that, the software
runs under your normal user account, as do all of the commands you







|







 







|
|
<
|
|
|
|







 







|
|
|
|
>






|
|
|

|
|
|
|
<







51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
...
615
616
617
618
619
620
621
622
623

624
625
626
627
628
629
630
631
632
633
634
...
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889

890
891
892
893
894
895
896
[os]: https://tangentsoft.com/pidp8i/wiki?name=OS+Compatibility


<a id="unpacking"></a>
## Getting the Software onto Your Pi

If you're reading this file within an unpacked distribution of the
PiDP-8/I software, you may skip this section, because you have
already achieved its aim.

If you are reading this [online][this] and have not yet downloaded and
unpacked the software source code onto your Pi, this section will get
you going.

[this]: https://tangentsoft.com/pidp8i/doc/trunk/README.md
................................................................................

In late 2017 [several of us][aut] created the `mkos8` tool, which was
replaced during 2018 by Bill Cattey with the `os8-run` interpreter
and its stock scripts. The `--*-os8-*` options documented above get
passed into `os8-run` during the PiDP-8/I software build process,
which controls how it generates the `v3d*.rk05` RK05 disk image files.

This set of disk images entirely replaces the old `os8.rk05` disk image,
in that all features of the old disk image are still available. In some

cases, features present on the old `os8.rk05` disk are now left out or
disabled by default, and in other cases we have changed the behavior of
features from the way they used to be on the old disk. Mostly, though,
the new disk images are simply more functional than the old ones.

If you wish to know the full details of how these disk images are
created, see the documentation for [`os8-run`][ori] and that for
[`class simh`][cs].

The remainder of this section describes some aspects of these disk
images which are not clear from the descriptions of the `--*-os8-*`
................................................................................
keys if they are missing on boot, so you need to do this once by hand:

    $ sudo dpkg-reconfigure openssh-server

You should be able to log in via SSH immediately after that command
completes.

You may be wondering why we don’t do this automatically, somehow. It’s
because, over time, we’ve removed all dependence on root access in our
software in the name of security, so that we no longer have permission
to make system-wide changes like this in our startup scripts.  We now
rely on you, the system’s administrator, to do it interactively with
`sudo` permissions.


<a id="systemd" name="unit"></a>
## The systemd Unit File

Older stable releases of the PiDP-8/I software used an [old-style System
V init script][svinit] to start the PiDP-8/I service. This includes
Oscar Vermeulen's final stable release.

Starting with release v2019.04.25, we have now switched to a
[systemd][systemd] unit file, since Raspbian has been systemd-based for
years. (It also supports SysV init scripts, but only as a second-class
mechanism intended for backwards compatibility only.)


One of the features systemd gives us is the ability to set the unit
to run as user-level service rather than as a system-wide service,
which means you no longer need the `sudo` prefix on commands to start,
stop, restart, and query the service. The only time you now need root
privileges is when installing the software. After that, the software
runs under your normal user account, as do all of the commands you