Warren, Thanks for the comment. I appreciate your feedback and will make appropriate changes. Next? I have been reading Lyons and it has taken me some time to develop enough background knowledge to make sense of his notes. A surface read of the notes will give a novice reader some idea of the major architectural components of the system, but a deeper read will require the reader to have knowledge beyond what is required of most modern software developers (PDP-11 architecture, assembly language, and UNIX are prerequisite). It will also require access to a lab where the ideas covered can be experimented with. A modern reader might be intrigued from a historical perspective, but may not be compelled to go to the trouble of learning enough about the past to recreate it or even see the its relevance to the present or future. Access in 2015 to a working UNIX v6 environment on a PDP-11 ala 1975 is as unlikely as it sounds. However, using SimH to simulate a functional PDP-11, with peripherals, a UNIX v6 tape image from 1975, and the documentation from that period, which, thanks to TUHS is now accessible, it becomes possible to establish a laboratory from which to experiment. The resulting environment is not only historically interesting, but technically interesting, as well. Many of the interesting bits about our current systems, even seemingly unexplainable things like magic numbers, have their genesis and rational in this early system. The v6 kernel weighs in at around 10k lines of code with a limited set of peripherals and yet it packs in features that were either unavailable in larger more established systems or may have been present in some form, but were orders of magnitude more lines of code and attendant complexity. It was and remains an amazing operating system and worthy of contemporary study. So, I was thinking that next up, I would write up notes to help the modern reader engage with v6 more easily in order to follow works like Lyons. Right now, I am working on notes related to using the v6 assembly and c languages to produce working code. While this may seem trivial to folks who are expert, or who have worked in the actual environments, it is not really so trivial for me or for other folks brought up on more modern computing platforms and I would like to both understand the workflows and to document them for others. Regards, Will

Dave, Thanks for catching this. I have no idea where I got Lyons from. Sheesh, I have his book right here on the table... I will make appropriate edits. Regards, Will On 12/2/15 10:11 PM, Dave Horsfall wrote:

Peter Jeremy scripsit: Joseph Nathaniel Lyons himself had nothing to do with the computer, of course. But then again, Emack and Bolio had nothng to do with the ice-cream store, either. -- John Cowan http://www.ccil.org/~cowan cowan(a)ccil.org Time alone is real the rest imaginary like a quaternion --phma

On Friday, 4 December 2015 at 17:22:09 +1100, Dave Horsfall wrote: Take a look at CSIRAC in the Melbourne museum, the oldest computer in the world. It's worth it, even if they don't have it running. Greg -- Sent from my desktop computer. Finger grog(a)FreeBSD.org for PGP public key. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft MUA reports problems, please read http://tinyurl.com/broken-mua

Greg 'groggy' Lehey scripsit: Well, there's the Antikythera mechanism. -- John Cowan http://www.ccil.org/~cowan cowan(a)ccil.org In the sciences, we are now uniquely privileged to sit side by side with the giants on whose shoulders we stand. --Gerald Holton

Hello! We are also forgetting the contraption that Turing built. Of course sadly at the end it was destroyed. Why? I don't know. But it has since been rebuilt. ----- Gregg C Levine gregg.drwho8(a)gmail.com "This signature fought the Time Wars, time and again." On Fri, Dec 4, 2015 at 1:17 PM, Ronald Natalie <ron(a)ronnatalie.com> wrote: