[TUHS] Re: running BSD 2.11 on my PDP 11/70 emulator

It is the BSD kernel or the emulator setup I question as to being correct. The clues being An almost 4 mb available memory coupled to a roughly 300 kb user space. The 300kb doesn't make sense at all from the limits of the split i/d memory layout. It's roughly 10% of available. It's inferring that the kernel itself is being configured as a 3.5 mb runtime image. Almost as if dynamic kernel level buffers are being over allocated by a configuration parameter or a miscalculation. The other clue being the dump of the printf style format strings from the data portion of the involved user space program images as it boots. That's the sign of a wrong address potentially being used. An address fault causing an abend happening to multiple binaries being launched for example These are the anomalies I see. The solution requires someone very familiar with the bsd 2.11 boot up sequence and the underlying executables involved. I am a V6, v7. System V head. Unfortunately Mr. Jolitz is no longer with us. As I recall, the bsd folks were back porting some of the features of the Vax virtual version of the bsd kernel as appropriate to the pdp version. I dont recall what was involved in that effort. The source code environment for 2.11 would help. I also don't know if those failure messages are coming from the bsd image handling address faults etc. or the actual emulator underneath detecting problems in the binary as it executes it. So the questions to be answered are 1. Why is the user memory only 10% of the available? 2. What is dumping and the "why of it" the text strings in the data space portion of the program image? I don't the answer. But it all strikes me as odd. On Mon, Apr 7, 2025, 12:15 PM Ron Natalie <ron(a)ronnatalie.com> wrote: