From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 24675 invoked from network); 7 Oct 2022 05:03:51 -0000 Received: from minnie.tuhs.org (50.116.15.146) by inbox.vuxu.org with ESMTPUTF8; 7 Oct 2022 05:03:51 -0000 Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id 0DE9240EA2; Fri, 7 Oct 2022 15:03:16 +1000 (AEST) Received: from mail-pg1-f176.google.com (mail-pg1-f176.google.com [209.85.215.176]) by minnie.tuhs.org (Postfix) with ESMTPS id 374C740EA1 for ; Fri, 7 Oct 2022 15:03:10 +1000 (AEST) Received: by mail-pg1-f176.google.com with SMTP id s206so3690387pgs.3 for ; Thu, 06 Oct 2022 22:03:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kev009.com; s=google; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=3J7Gc/Ekq7/6slzZqvnAIDzl4z8zjA+x4SP6WCmm6mE=; b=dh1epM66v6qDapV8/5bUoIm8j4zqj2QT81yR2gFvtrQCqsM8ocqJRr+H3cAJwHcKhY CH9kxHDIl862qF4DanDZJ66OY6Vz8f7SLOaPizzl2oGcRKsEsdbQt9s+on4zc73wdSIK zRT9U7gVgzjBaoZmVXgAmxtVQaPwa+avvFePs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=3J7Gc/Ekq7/6slzZqvnAIDzl4z8zjA+x4SP6WCmm6mE=; b=taDjHa5gAi+Qgo/UVal8ADSTrN90Qo2XUMbwuFbAcNW6wQBuYPmlvUoiBIUEBQsXdy 07nNtB0v4rIba02gDh1pDz0sjmXvuR22MEdo/fVP7i9eSpAvO9biQ2R6mucs2vCmd+TA SIgvVS1Z2vE7k+T5zEJxUfVf04n4LuVuLS4UNQPhRRkDPca6YPM5m0bQ+t5mySS/88R5 KCism+ZXYQfGD5LwrK7YVS8H5WxMOGlOGvObJPTdNq3/GPV0mn85k7J/mJoIAbtY/sZl TY6mzrviZ5TeeJ7qvoDAUYOCGAhpfEmsuRYzDWmY0zrQ1W7OGfUC6m3SaZL0ZIL+/38M dATQ== X-Gm-Message-State: ACrzQf0VZGaAHEXtONCt9sWCueqb1L/k6JQ7kP55CQgEpXZ5bkAFa/av tLC/HHPruh/dcXAB8mo6YqJMYPrhrwGmOoWgr5bcgNq7Nyc= X-Google-Smtp-Source: AMsMyM7rdGnvnoVNdQbTqIYb6vbhxFYYvaX8Okr6pqKF16OOxmX8k3VkUjSC2+ZBathQyeuEBKw2gLJPNmJejdAS2sw= X-Received: by 2002:a62:1791:0:b0:562:2298:b33c with SMTP id 139-20020a621791000000b005622298b33cmr3392313pfx.25.1665118929528; Thu, 06 Oct 2022 22:02:09 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Kevin Bowling Date: Thu, 6 Oct 2022 22:01:57 -0700 Message-ID: To: segaloco Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Message-ID-Hash: XEKDNRAVE5JJGAZUZEPW6OISM7DFHNRE X-Message-ID-Hash: XEKDNRAVE5JJGAZUZEPW6OISM7DFHNRE X-MailFrom: kevin.bowling@kev009.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tuhs.tuhs.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: The Eunuchs Hysterical Society X-Mailman-Version: 3.3.6b1 Precedence: list Subject: [TUHS] Re: Documentation Call Numbers and Meanings? List-Id: The Unix Heritage Society mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Thu, Oct 6, 2022 at 9:34 PM Kevin Bowling wro= te: > > On Mon, Oct 3, 2022 at 2:05 PM segaloco via TUHS wrote: >> >> Good afternoon folks, linked is a list of all of the call numbers of UNI= X-relevant documentation that I've been able to catalogue lately: https://p= astebin.com/DbDAhX3W >> >> This isn't exhaustive, I skipped many documents under dept (assuming dep= t) 305, 306, and 308, focusing mainly on 700, 301, 307, and 320. >> >> I was wondering if anyone that has some knowledge of the numbering syste= m used for these documents in Bell might be able to comment on this in any = way. What I've been able to make some determination on is: > > > The numbering system seems vaguely similar to BSPs ( > https://en.wikipedia.org/wiki/Bell_System_Practices). > > There are top level BSP sections for the 3B2 and 3B20 among other interes= ting history to this community. For some reason the telephone community ha= sn=E2=80=99t done a good job of digitizing the complete BSPs nor a modern i= ndex (I physically browsed an index from the early 90s but someone disappea= red it from where I did so). I=E2=80=99ve heard are private collectors wit= h complete collections of some vintage. Checked my notes, for the BSPs in case someone comes across them: 254- 3B20D 555- 3B2 585- 3B5 >> >> 700-prefixed call numbers appear to be general Western Electric stuff, m= ost of these manuals being related to switching, power, hardware, etc. Howe= ver, the UNIX 3.0 manual and 4.0 reference guide are both under this series= too. I imagine this was simply because the computer systems group hadn't b= een formally spun off or otherwise received directive to manage UNIX docume= ntation at this point? In any case, I'd be curious what all else may have g= otten 700-series call numbers before the 300-series took over UNIX docs. >> >> As for the 300 series, as far as I can tell 300 is the umbrella for AT&T= Computer Systems, with several sub departments handling slightly different= (although overlapping in circumstances) concerns. What I have managed to d= etermine is that 301 series encompasses the original System V version docum= entation, a few "Level II COBOL" documents, as well as some M68000 and Z800= 0-specific versions of docs (I didn't know UNIX System V ever hit the Z8000= , that's cool). >> >> After System V gold, the wealth of UNIX documentation appears to come fr= om code 307-X instead, I'm assuming 307 is whatever permutation of USG/USL = happened to exist at the time. However, there are a few other codes that se= em to sporadically be involved in UNIX docs as well as other computing docs= : >> >> 302 - Just a smattering of Writers Workbench docs, very high call number= suffixes (950-958). >> >> 303 - Bunch of 3B20D (Real-Time-Reliable) docs as well as other 3B20 stu= ff, mainly hardware manuals but a few SVR2.1-related docs as well for 3B20A= , S, and D >> >> 304 - Another smattering of 3B20 docs, this time mostly A and S, mix of = hardware and UNIX docs >> >> 305 - This one is hard to pin down, they've got the basic 3B2 docs, some= other guidance docs for non-20 3B computers, and a mishmash of language to= ols like assemblers, a BASIC interpreter, compilers, and a few odd technica= l bulletins for products covered in other groups >> >> 306 - There wasn't much direct UNIX documentation here, just stuff about= 3BNet (3B computer networking?) and the 5620 DOT Mapped terminal >> >> 308 - Documentation on a whole mess of software utilities with some odd = Sys V manuals sprinkled in. You've got stuff like the "Office Telesystem", = Instructional Workbench, more docs on BASIC, Pascal, and COBOL, some Fortra= n stuff as well, and a few other reference documents >> >> 310 - Seems to be entirely related to Documenter's and Writer's Workbenc= hes. Whats odd is there is also a pretty even split of DWB and WWB document= s in the 302 and 307 groups, so hard to say why the split, maybe a secondar= y department producing supplementary literature? Very low call number suffi= xes, so possibly 302 transitioned into 310 for DWB/WWB support >> >> 311 - Might be a "trade book" publishing arm, seems to only contain a fe= w books, including "The C Programming Language" >> >> 320 - Might be the "standard systems" trade books arm as opposed to the = version/system specific documentation gotten from USL directly. This list c= ontains books like the SVID, Bach's Design of the UNIX Operating System boo= k, some programming guidance books, and the UNIX Programmer's Manual 5 volu= me series with the metallic alphabet blocks on the cover (echoing the V7 tr= ade release). What's interesting is call number 320-X comes back around wit= h SVR4 as the call code that a number of 386-specific manuals were publishe= d under. >> >> 341 - This one is very odd, a higher call number than any of the others,= but the only docs I could find under this are the System V gold Document, = Graphics, Programming, and Support Tools guides, which curiously weren't pu= blished under 301 like the rest of the documentation for that version. >> >> Finally, some digestion from this research: >> This gives some compelling version-support information in early SysV I w= asn't aware of previously: >> >> System V Gold: >> >> PDP-11 >> VAX-11 >> 3B >> M68000 >> Z8000 >> >> System V R2: >> >> VAX-11 >> 3B >> M68000 >> NS32000 >> iAPX 286 >> >> >> It appears Bell also opted to have different documentation sets for diff= erent processors in SVR2. We kinda see this later on with i386 variants of = the SVR3 and SVR4 documents, but I don't think we ever quite see this wide = of a spread of docs straight from AT&T after this. >> >> Also, among the many documents (one I didn't add to the list yet) is one= referring specifically to UNIX Release 5.3, not System V R3 or anything li= ke that, but a Release 5.3. I know I've seen "Release 5.2" listed in a few = places, which had me curious, is there a well established record of what ha= ppened with internal (non research) UNIX after System V was branched? Wheth= er the development stream simply became System V development, or if there w= as still a totally separate UNIX 5.x branch for a while that, while borrowe= d into System V at necessary times, did still constitute a distinct branch = of development after the initial System V release. I know there is at least= evidence of aspects of System V being put into CB UNIX 2.3, meaning CB 2.3= was post-System V, that would make a compelling argument for there being s= ome more development work between CB and USG folks before they put the fina= l bow on the UNIX/TS project and formally routed all efforts to System V. >> >> I'm sure there are other little nuggets of information hiding in there, = but that's my digest from this thus far. If anyone knows of any other such = efforts to produce a listing of all known UNIX documentation call numbers f= rom AT&T, I'll happily contribute this to their efforts. >> >> - Matt G. >> >> P.S. SysV Gold scans are still inbound, just likely will be a winter pro= ject once the rains start and I can't go play outside. >>