TUHS July 2024

tuhs@tuhs.org

60 participants
27 discussions

Fwd: DKUUG, EUUG and 586 issues (3700+ pages) of Unigram-X 1988…1996

by Warren Toomey

All ... ----- Forwarded message from Poul-Henning Kamp ----- Subject: DKUUG, EUUG and 586 issues (3700+ pages) of Unigram-X 1988…1996 (Please forward to the main TUHS list if you think it is warranted) A brief intro: Datamuseum.dk is a volunteer-run effort to collect, preserve and present "The Danish IT-history". UNIX is part of that history, but our interest is seen through the dual prisms of "Danish IT-History" and the computers in our collection. My own personal UNIX interest is … [View More]of course much deeper and broader, which is why I'm sending this email. Recently we helped clean out the basement under the Danish Unix User's Group (DKUUG) which is winding down, and we hauled of a lot of stuff, which includes much EUUG - (European Unix Users Group) material. As I feed it through the scanner, the EUUG-newsletters will appear here: https://datamuseum.dk/wiki/Bits:Keyword/PERIODICALS/EUUG-NEWSLETTER And proceedings from EUUG conferences (etc.) will appear here: https://datamuseum.dk/wiki/Bits:Keyword/DKUUG/EUUG I also found four boxes full of "Unigram-X" newsletters. Unigram-X was a newsletter, published weekly out of London. A typical issue was two yellow A3 sheets folded, or if if news was slight, a folded A3 with an A4 insert. … and that is just about all I know about it. But whoever wrote it, they clearly had an amazing Rolodex. In total there a tad more than 3700 pages of real-time news and gossip about the UNIX world from 1986 to 1996. It's not exactly core material for datamuseum.dk, but it is a goldmine for UNIX history, so I have spent two full days day scanning and getting all the pages, sorted, flipped and split into one-year-per-pdf files. I should warn that neither the raw material nor the scan is perfect, but this is it, unless somebody else feels like going through it again. (The paper stays in our collection, no rush.) I need to go through and check for pages being upside down or out of order, before I ingest the PDFSs into the Datamuseum.dk bitarchive, but here is a preview: https://phk.freebsd.dk/misc/unigram_x_1986_0034_0058.pdf https://phk.freebsd.dk/misc/unigram_x_1987_0059_0108.pdf https://phk.freebsd.dk/misc/unigram_x_1988_0109_0159.pdf https://phk.freebsd.dk/misc/unigram_x_1989_0160_0211.pdf https://phk.freebsd.dk/misc/unigram_x_1990_0212_0262.pdf https://phk.freebsd.dk/misc/unigram_x_1991_0263_0313.pdf https://phk.freebsd.dk/misc/unigram_x_1992_0314_0365.pdf https://phk.freebsd.dk/misc/unigram_x_1993_0366_0416.pdf https://phk.freebsd.dk/misc/unigram_x_1994_0417_0467.pdf https://phk.freebsd.dk/misc/unigram_x_1995_0468_0518.pdf https://phk.freebsd.dk/misc/unigram_x_1996_0519_0616.pdf My ulterior motives for this preview are several: If you find any out-of-order or rotated pages, please let me know. It's not a complete collection, the following issues are missing: 1…33 35 39…49 86…87 105 138 229 321 400 405…406 496 498 507 520 523…524 527…528 548 613 615 617… It would be nice to fill the holes. As a matter of principle, we do not store OCR'ed PDF's in the datamuseum.dk bitarchive[1], and what with me still suffering from a job etc, I do not have the time to OCR 3700+ pages under any circumstances. But even the most crude and buggy OCR reading would be a great resource to grep(1), so I'm hoping somebody else might find the time and inclination ? And a "best-of-unigram-x" page on the TUHS wiki may be warranted, because there are some seriously great nuggets in there :-) Enjoy, Poul-Henning [1] I'm not entertaining any arguments about this: We're trying to align with best practice in historical collection world. The argument goes: Unless the OCR is perfect, people will do a text-search, not find stuff, and conclude it is not there. Such interpretations of artifacts belong in peer-reviewed papers, so there is a name of who to blame or praise, and so that they can be debated & revised etc. [2] The PDF's are archive-quality, you can extract the raw images from them, for instance with XPDF's "pdfimages" program. ----- End forwarded message ----- [View Less]

8 months, 2 weeks

Re: machine code translation,as mental architecture models

by jnc＠mercury.lcs.mit.edu

> From: Dan Cross > These techniques are rather old, and I think go back much further than > we're suggesting. Knuth mentions nested translations in TAOCP .. > suggesting the technique was well-known as early as the mid-1960s. I'm not sure what exactly you're referring to with "[t]hese techniques"; I gather you are talking about the low-level mechanisms used to implement 'system calls'? If so, please permit me to ramble for a while, and revise your time-line somewhat. … [View More] There are two reasons one needs 'system calls'; low-level 'getting there from here' (which I'll explain below), and 'switching operating/protection domains' (roughly, from 'user' to 'kernel'). In a batch OS which only runs in a single mode, one _could_ just use regular subroutine calls to call the 'operating system', to 'get there from here'. The low-level reason not to do this is that one would need the addresses of all the routines in the OS (which could change over time). If one instead used permanent numbers to identify system calls, and had some sort of 'system call' mechanism (an instruction - although it could be a subroutine call to a fixed location in the OS), one wouldn't need the addresses. But this is just low level mechanistic stuff. (I have yet to research to see if any early OS's did use subroutine calls as their interface.) The 'switching operating/protection domains' is more fundamental - and unavoidable. Obviously, it wouldn't have been needed before there were machines/OS's that operated in multiple modes. I don't have time to research which was the _first_ machine/OS to need this, but clearly CTSS was an early one. I happen to have a CTSS manual (two, actually :-), and in CTSS a system call was: TSX NAMEI, 4 .. .. NAMEI: TIA =HNAME where 'NAME' "is the BCD name of a legitimate supervisor entry point", and the 'TIA' instruction may be "usefully (but inexactly) read as Trap Into A core" (remember that in CTSS, the OS lived in the A core). (Don't ask me what HNAME is, or what a TSX instruction does! :-) So that would have been 1963, or a little earlier. By 1965 (see the 1965 Fall Joint Computer Conference papers: https://multicians.org/history.html for more), MIT had already moved on to the idea of using a subroutine calls that could cross protection domain boundaries for 'system calls', for Multics. The advantage of doing that is that if the machine has a standard way of passing arguments to subroutines, you natively/naturally get arguments to system calls. Noel [View Less]

8 months, 2 weeks

Reminder: use the right list

by Warren Toomey

All, just a friendly reminder to use the TUHS mailing list for topics related to Unix, and to switch over to the COFF mailing list when the topic drifts away from Unix. I think a couple of the current threads ought to move over to the COFF list. Thanks! Warren

8 months, 2 weeks

Re: mental architecture models, Anyone ever heard of teaching a case study of Initial Unix?

by Douglas McIlroy

> In order to port VMS to new architectures, DEC/HP/VSI ... > turned the VAX MACRO assembly language (in which > some of the VMS operating system was written) into a > portable implementation language by 'compiling' the > high-level CISC VAX instructions (and addressing modes) > into sequences of RISC instructions. Clem Pease did the same thing to port TMG from IBM 7000-series machines to the GE 600 series for Multics, circa 1967. Although both architectures had 36-bit words,… [View More]

8 months, 2 weeks

Anyone ever heard of teaching a case study of Initial Unix?

by sjenkin＠canb.auug.org.au

I’ve never heard of a Computer Science or Software Engineering program that included a ‘case study’ component, especially for Software Development & Projects. MBA programs feature an emphasis on real-world ‘case studies’, to learn from successes & failures, to give students the possibility of not falling into the same traps. Creating Unix V6, because it profoundly changed computing & development, would seem an obvious Case Study for many aspects of Software, Coding and Projects. … [View More]There have been many descriptive treatments of Initial Unix, but I’ve never seen a Case Study, with explicit lessons drawn, possibly leading to metrics to evaluate Project progress & the coding process. Developers of Initial Unix arguably were 10x-100x more productive than IBM OS/360, a ‘best practice’ development at the time, so what CSRC did differently is worth close examination. I’ve not seen examined the role of the ‘capability’ of individual contributors, the collaborative, collegiate work environment and the ‘context’, a well funded organisation not dictating deadlines or product specifications for researchers. USG, then USL, worked under ’normal commercial’ management pressure for deadlines, features and specifications. The CSRC/1127 group did have an explicit approach & principles for what they did and how they worked, publishing a number of books & papers on them - nothing they thought or did is secret or unavailable for study. Unix & Unix tools were deliberately built with explicit principles, such as “Less is More”. Plan 9 was also built on explicit Design principles. The two most relevant lessons I draw from Initial Unix are: - the same as Royce's original “Software Waterfall” paper, “build one to throwaway” [ albeit, many, many iterations of the kernel & other code ] - Writing Software is part Research, part Creative ‘Art’: It’s Done when it's Done, invention & creation can’t be timetabled. For the most reliable, widely used Open Source projects, the “Done when it’s Done” principle is universally demonstrated. I’ve never seen a large Open Source project succeed when attempting to use modern “Project Management” techniques. These Initial Unix lessons, if correct and substantiated, should cause a revolution in the teaching & practice of Professional Programming, i.e. Programming In the Large, for both CS & SW. There are inherent contradictions within the currently taught Software Project Management Methodologies: - Individual capability & ability is irrelevant The assumption is ‘programmers’ are fungible/ identical units - all equally able to solve any problem. Clearly incorrect: course evaluations / tests demonstrate at least a 100x variance in ability in every software dimension. - Team environment, rewards & penalties and corporate context are irrelevant, Perverse incentives are widely evident, the cause of many, or all, “Death Marches”. - The “Discovery & Research Phases” of a project are timetabled, an impossibility. Any suggestions for Case Studies gratefully accepted. =========== Professions & Professionals must learn over time: there’s a negative aspect (don’t do this) and positive aspect (do this) for this deliberate learning & improvement. Negatives are “Don’t Repeat, or Allow, Known Errors, Faults & Failures” plus in the Time Dimension, “Avoid Delays, Omissions and Inaction”. Positives are what’s taught in Case Studies in MBA courses: use techniques & approaches known to work. Early Unix, from inception to CACM papers, 1969 to 1974, took probably 30 man-years, and produced a robust, performant and usable system for it’s design target, “Software Development”. This in direct comparison to Fred Brooks IBM OS/360 effort around 5 years before that consumed 3,000-4,000 man-years was known for bugs, poor & inconsistent code quality, needed large resource to run and was, politely, non-performant. This was a commercial O/S, built by a capable, experienced engineering organisation, betting their company on it, who assigned their very best to the hardware & software projects. It was “Best of Breed” then, possibly also now. MULTICS had multiple business partners, without the same, single focus or commercial imperative. I don’t believe it’s comparable to either system. Initial Unix wasn’t just edit, compile & run, but filesystems, libraries, debugging & profiling tools, language & compiler construction tools, ‘man’ pages, document prep (nroff/troff) and 'a thousand' general tools leveraging shell / pipe. This led directly to modern toolchains, config, make & build systems, Version Control, packaging systems, and more. Nothing of note is built without using descendants or derivatives of these early toolchains. All this is wrapped around by many Standards, necessary for portable systems, even based on the same platform, kernel and base system. The “Tower of Babel” problem is still significant & insurmountable at times, even in C-C & Linux-Linux migration, but without POSIX/IEEE standards the “Software Tarpit” and "Desert of Despair” would’ve been unsolvable. The early Unix system proved adaptable and extensible to many other environments, well beyond “Software Development”. =========== [ waterfall model ] Managing the development of large software systems: concepts and techniques W. W. Royce, 1970 [ free access ] <https://dl.acm.org/doi/10.5555/41765.41801> STEP3: DO IT TWICE, pg 334 After documentation, the second most important criterion for success revolves around whether the product is totally original. If the computer program in question is being developed for the first time, arrange matters so that the version finally delivered to the customer for operational deployment is actually the second version insofar as critical design/operations areas are concerned. =========== Plan 9, Design <https://9p.io/sys/doc/9.html> The view of the system is built upon three principles. First, resources are named and accessed like files in a hierarchical file system. Second, there is a standard protocol, called 9P, for accessing these resources. Third, the disjoint hierarchies provided by different services are joined together into a single private hierarchical file name space. The unusual properties of Plan 9 stem from the consistent, aggressive application of these principles. =========== Escaping the software tar pit: model clashes and how to avoid them Barry Boehm, 1999 [ free access ] <https://dl.acm.org/doi/abs/10.1145/308769.308775#> =========== Mythical Man-Month, The: Essays on Software Engineering, Anniversary Edition, 2nd Edition Fred Brooks Chapter 1. The Tar Pit Large-system programming has over the past decade been such a tar pit, and many great and powerful beasts have thrashed violently in it. =========== -- Steve Jenkin, IT Systems and Design 0412 786 915 (+61 412 786 915) PO Box 38, Kippax ACT 2615, AUSTRALIA mailto:sjenkin@canb.auug.org.au http://members.tip.net.au/~sjenkin [View Less]

8 months, 3 weeks

Is There Teletype DNA In the Blit?

by segaloco

I suppose this question is best directed at Rob or Doug, but just might as well ask at large: Given AT&T's ownership of Teletype and the involvement (AFAIK) of Teletype with other WECo CRT terminals (e.g. Dataspeed 40 models), was there any direct involvement of folks from the Teletype side of things in the R&D on the Jerq/Blit/DMD? Or was this terminal pure Bell Labs? - Matt G.

8 months, 3 weeks

Program Generic Issue 3 Init System?

by segaloco

Good afternoon, I was wondering if anyone currently on list is in possession of a copy of the UNIX Programmer's Manual for Program Generic Issue 3 from March of 1977. This is the version nestled between Issue 2 which Al Kossow has preserved here: http://www.bitsavers.org/pdf/att/unix/6th_Edition/UNIX_Programmers_Manual_1… and the MERT 0 release provided by I believe Heinz Lycklama here: https://www.tuhs.org/Archive/Documentation/Manuals/MERT_Release_0/ If I might make a request of anyone … [View More]

8 months, 3 weeks

Re: mental architecture models, Anyone ever heard of teaching a case study of Initial Unix?

by jnc＠mercury.lcs.mit.edu

> From: Steve Jenkin > C wasn't the first standardised coding language, FORTRAN & COBOL at > least were before it There were a ton; Algol-60 is the most imppotant one I can think of. (I was thinking that Algol-60 was probably an important precursor to BCPL, which was the predecessor to C, but Richards' first BCPL paper: https://dl.acm.org/doi/10.1145/1476793.1476880 "BCPL: A tool for compiler writing and system programming" doesn't call it out, only CPL. However, CPL … [View More]

8 months, 3 weeks

3B21D

by Kevin Bowling

Howdy, I now have this pictured 3B21D in my facility http://kev009.com/wp/2024/07/Lucent-5ESS-Rescue/ It will be a moment before I can start work on documentation of the 3B21D and DMERT/UNIX-RTR but wanted to share the news. Regards, Kevin

8 months, 3 weeks

Any Surviving LIL Compilers/Code Artifacts?

by segaloco

So I'm doing a little bit of the footwork in prep for analyzing manual differences between Research, Program Generic, and PWB/UNIX, and found something interesting. The LIL Programming Language[1] was briefly available as a user-supported section 6 command on Fifth Edition (1974) UNIX, appearing as a page but not even making it into the TOC. It was gone as quickly as it appeared in the Research stream, not surviving into V6. However, with Al Kossow's provided Program Generic Issue 2 (1976) … [View More]

8 months, 3 weeks

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

1994

1993

1992

1991

1990

TUHS July 2024