[geek1011]

Originally Posted by davidfor

From what I have been told, the read-only attribute was being respected well before that.

That's actually true... I'm surprised nobody (including myself) noticed it before this (I only noticed it when looking into the missing Dictionary table in this version).

Spoiler:

for ln in kp/*/libnickel.so.1.0.0; do strings "$ln" | grep read-only && echo "$ln"; done
marked as read-only.. skipping
kp/11655/libnickel.so.1.0.0
marked as read-only.. skipping
kp/11911/libnickel.so.1.0.0
marked as read-only.. skipping
kp/11976/libnickel.so.1.0.0
marked as read-only.. skipping
kp/11980/libnickel.so.1.0.0
marked as read-only.. skipping
kp/11982/libnickel.so.1.0.0
marked as read-only.. skipping
kp/12019/libnickel.so.1.0.0
marked as read-only.. skipping
kp/12111/libnickel.so.1.0.0
marked as read-only.. skipping
kp/12638/libnickel.so.1.0.0
marked as read-only.. skipping
kp/12777/libnickel.so.1.0.0
marked as read-only.. skipping
kp/12920/libnickel.so.1.0.0
marked as read-only.. skipping
kp/13162/libnickel.so.1.0.0
marked as read-only.. skipping
kp/13337/libnickel.so.1.0.0
marked as read-only.. skipping
kp/13651/libnickel.so.1.0.0
marked as read-only.. skipping
kp/13694/libnickel.so.1.0.0
marked as read-only.. skipping
kp/13737/libnickel.so.1.0.0
marked as read-only.. skipping
kp/14123/libnickel.so.1.0.0
marked as read-only.. skipping
kp/14601/libnickel.so.1.0.0
marked as read-only.. skipping
kp/14617/libnickel.so.1.0.0
marked as read-only.. skipping
kp/14622/libnickel.so.1.0.0