That's odd. I just tried it on my PiDP-11 and got:
terri@spcpi2-host:~ $ sudo setcap cap_net_raw,cap_net_admin=eip /opt/pidp11/src/02.3_simh/4.x+realcons/bin-rpi/pdp11_realcons
terri@spcpi2-host:~ $
Please try the following two commands:
which setcap
find /opt -name pdp11_realcons
On my system, I get:
terri@spcpi2-host:~ $ which setcap
/usr/sbin/setcap
terri@spcpi2-host:~ $ find /opt -name pdp11_realcons
/opt/pidp11/bin/backupAmd64-binaries/pdp11_realcons
/opt/pidp11/bin/backup32bit-binaries/pdp11_realcons
/opt/pidp11/bin/backup64bit-binaries/pdp11_realcons
/opt/pidp11/src/02.3_simh/4.x+realcons/bin-rpi/pdp11_realcons
terri@spcpi2-host:~ $
Trixie support is mostly (pretty much entirely, actually) untested. Current development
is happening under Bookworm and once that is solid, I'll see what extra work is needed
for Trixie. Some people over in the PiDP-10 group reported problems with Trixie, and at
least one PiDP-11 user here had to give up and start over with Bookworm (which fixed
their issues). The Raspberry Pi organization just released Trixie in October, and I notice
that they re-rolled the kits at the beginning of this month, so it seems to still be working
on becoming stable for production use,
Oscar's obsolescence GitHub repo has an install script that does some things (including
this 'setcap') in the wrong order. Re-running it may (or may not) correct the issue, but
using the setcap command I provided should get you going. If you typed it in by hand,
it is long and has some oddball characters, so I recommend using cut/paste to issue the
command. Remember that reading this group on the web (or possibly via email) may
wrap the command line. The whole thing from 'sudo' through 'realcons' is all one com-
mand line.