@wohali, Strange that the images have gone missing. I'm pretty sure I attached them to the posts, which should mean they were hosted by the vcfed.org server. (I'm also not getting email notifications for @ mentions, so sorry for the delay).
Anyway, here are the original pictures.
The...
Version number in that position makes a lot of sense, although maybe its some sort of bit field, since 0x10/16 seems like a pretty number for something that probably didn't change all that much.
I gleaned the max and min numbers from what diskutil would accept. It may be that the Xenix hd...
Anyone know the format of the ".pvh" table that is written to the first sector of the disk by the Xenix diskutil tool? I think I've figured out most of it. But there are a couple of fields that are still a mystery.
Here's what I have so far:
Byte Offset
Length...
You get to do that. All you need is a fixed, unique sequence of bytes, preferably placed at a known location in the file (right at the beginning is good). An 8 byte sequence is the minimum I would use in this case, since you're not really space constrained. But 4 would work.
It doesn't matter...
I have a UC07 that I have used in a QBUS PDP-11 with various CPU configurations (M8186, M8189, M8192) and in a QSUB MicroVAX (M7620 / KA650). In all cases I booted some form of BSD (2.9, 2.11 and 4.3).
Exactly. Although I think a hash of the header data, including the magic number, could be good as well.
I bring this up because at the moment I'm busy adding support for various virtual disk container formats to my retro-fuse project. This is happening as part of my effort to support mounting...
Congrats on your new acquisition! I also found the console connector confusing when I first got my '05. To help me wrap my head around it I put together the following doc which shows the connector pin numbering and signal assignments, as seen from the back of the system...
Actually, it looks like each swapped out process maintains it's size in the proc p_size field. That plus a global pointing to the first unused swap block could be used to compute the parent process's first swap block on process exit/swap-in.
I have to say, I like the non-BGOPTION process model...
This is interesting. I'd always assumed that swapping in LSX worked the same as in Mini-Unix (where swap space is allocated based on process id). I see now that it is, but only when BGOPTION is enabled. I wonder why the non-preemtive option (BGOPTION undefined) wasn't included in Mini-Unix.
Nice work! I too am fascinated by early Unixes running on low-end PDPs, and the thought of what might have been had someone continued their development. In my case, I’m working with Mini-UNIX (a descendant of LSX) running on the PDP-11/05. Its definitely fun to see 50 year old computer with...