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, HTML_MESSAGE,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 20956 invoked from network); 7 Oct 2022 04:35:51 -0000 Received: from minnie.tuhs.org (50.116.15.146) by inbox.vuxu.org with ESMTPUTF8; 7 Oct 2022 04:35:51 -0000 Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id 3361640139; Fri, 7 Oct 2022 14:35:41 +1000 (AEST) Received: from mail-pl1-f172.google.com (mail-pl1-f172.google.com [209.85.214.172]) by minnie.tuhs.org (Postfix) with ESMTPS id 57BCD4010C for ; Fri, 7 Oct 2022 14:35:27 +1000 (AEST) Received: by mail-pl1-f172.google.com with SMTP id b2so3527144plc.7 for ; Thu, 06 Oct 2022 21:35:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kev009.com; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=2uC2/HQz2nJsBa/VwbqOeOM1nilOuOcAzdHP+Q1GYAM=; b=eNfjxoJLI2Lr/hJm/+HYxL153bDbs6wcAyxzl1Sxl5m8J0Fvl6VvovMZfAhOERGyx6 dM5EjbgiANKUCQIhAbcZtltH8n5Dp85twLgLiF9424RyoLIJFXtLgaZDpiwAzJ8JAEY6 sZKNsGgLpJLu8/c3bwQbQ85gPNNiAGZdhtHQI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=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=2uC2/HQz2nJsBa/VwbqOeOM1nilOuOcAzdHP+Q1GYAM=; b=8Q5PM0KRq14KsO9253mpCiNG617z8wm6n27E5Pb358JKsxwDN8XYsGf+IRfe9SiX7q 2EqQMLol1EMMk3w92b7RapO4Ps6sVfrmcreE2p49fnKxL6zcWsDQzHcK3rQlZ2l1lL0y HeHDErtrYRQHtXFFVIZo5x+/DPzvi9TA2ACr7kBYLCzMyLEEYKmAPy5/24Kgwsef59vV 4k/O5bwOBY+MB7shNtvx0x2B+gezl31W75N32thdrw/2DwP0pKfm1YXz79U7vxzDWI9X hEOyXQF8SZTgt8UaEXI9y95ehBMs0OQpmrHy5arbkzLoWH0J6Mc5PgRXkkkFKZ07Gyju /GAA== X-Gm-Message-State: ACrzQf3ipB+Lq87Ym0i4BuP2VVHmEs5EbZMCJlmNojOr/RORbDVK9Ra2 QTaEEMrwOd0rVeiGWMaB7MIcvn4/Nf4eQqFXOCA2Uw== X-Google-Smtp-Source: AMsMyM7ac++D9DOYualQcxAzkbR65z8EmfyiZg0pQ1Yriq/eZaVKR+ot7icB+cX5WJMEVwF27QfQOavbmhWdsJZYjPE= X-Received: by 2002:a17:90a:f8f:b0:20a:302f:92b8 with SMTP id 15-20020a17090a0f8f00b0020a302f92b8mr3267383pjz.80.1665117266372; Thu, 06 Oct 2022 21:34:26 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Kevin Bowling Date: Thu, 6 Oct 2022 21:34:15 -0700 Message-ID: To: segaloco Content-Type: multipart/alternative; boundary="0000000000002c012005ea6a53fc" Message-ID-Hash: H4EU7K3YJ3YL7KSAFMZVZHQ4LIZ6SKPT X-Message-ID-Hash: H4EU7K3YJ3YL7KSAFMZVZHQ4LIZ6SKPT 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: --0000000000002c012005ea6a53fc Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 > UNIX-relevant documentation that I've been able to catalogue lately: > https://pastebin.com/DbDAhX3W > > This isn't exhaustive, I skipped many documents under dept (assuming dept= ) > 305, 306, and 308, focusing mainly on 700, 301, 307, and 320. > > I was wondering if anyone that has some knowledge of the numbering system > 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 interesting history to this community. For some reason the telephone community hasn=E2=80=99t done a good job of digitizing the complete BSPs no= r a modern index (I physically browsed an index from the early 90s but someone disappeared it from where I did so). I=E2=80=99ve heard are private collec= tors with complete collections of some vintage. > 700-prefixed call numbers appear to be general Western Electric stuff, > most of these manuals being related to switching, power, hardware, etc. > However, 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 been formally spun off or otherwise received directive to manage > UNIX documentation at this point? In any case, I'd be curious what all el= se > may have gotten 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 differen= t > (although overlapping in circumstances) concerns. What I have managed to > determine is that 301 series encompasses the original System V version > documentation, a few "Level II COBOL" documents, as well as some M68000 a= nd > Z8000-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 fro= m > 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 > seem 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 > stuff, 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 > tools like assemblers, a BASIC interpreter, compilers, and a few odd > technical 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 > Fortran stuff as well, and a few other reference documents > > 310 - Seems to be entirely related to Documenter's and Writer's > Workbenches. Whats odd is there is also a pretty even split of DWB and WW= B > documents in the 302 and 307 groups, so hard to say why the split, maybe = a > secondary department producing supplementary literature? Very low call > number suffixes, so possibly 302 transitioned into 310 for DWB/WWB suppor= t > > 311 - Might be a "trade book" publishing arm, seems to only contain a few > 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 > contains books like the SVID, Bach's Design of the UNIX Operating System > book, some programming guidance books, and the UNIX Programmer's Manual 5 > volume series with the metallic alphabet blocks on the cover (echoing the > V7 trade release). What's interesting is call number 320-X comes back > around with SVR4 as the call code that a number of 386-specific manuals > were published 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 > published 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 > wasn'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 > different processors in SVR2. We kinda see this later on with i386 varian= ts > 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 > like 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 happened with internal (non research) UNIX after System V was > branched? Whether the development stream simply became System V > development, or if there was still a totally separate UNIX 5.x branch for= a > while that, while borrowed 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 p= ut > into CB UNIX 2.3, meaning CB 2.3 was post-System V, that would make a > compelling argument for there being some more development work between CB > and USG folks before they put the final 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 suc= h > efforts to produce a listing of all known UNIX documentation call numbers > from 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 > project once the rains start and I can't go play outside. > > --0000000000002c012005ea6a53fc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Oct 3, 2022 at 2:05 PM segaloco via TUHS <tuhs@tuhs.org> wrote:
Good afternoon folks, linked is a list of all of the call= numbers of UNIX-relevant documentation that I've been able to catalogu= e lately: https://pastebin.com/DbDAhX3W

This isn't e= xhaustive, I skipped many documents under dept (assuming dept) 305, 306, an= d 308, focusing mainly on 700, 301, 307, and 320.

I was wondering if anyone that= has some knowledge of the numbering system used for these documents in Bel= l might be able to comment on this in any way. What I've been able to m= ake 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 interesting history to this community.=C2=A0 F= or some reason the telephone community hasn=E2=80=99t done a good job of di= gitizing the complete BSPs nor a modern index (I physically browsed an inde= x from the early 90s but someone disappeared it from where I did so).=C2=A0= I=E2=80=99ve heard are private collectors with complete collections of som= e vintage.


700-prefi= xed call numbers appear to be general Western Electric stuff, most of these= manuals being related to switching, power, hardware, etc. However, the UNI= X 3.0 manual and 4.0 reference guide are both under this series too. I imag= ine this was simply because the computer systems group hadn't been form= ally spun off or otherwise received directive to manage UNIX documentation = at this point? In any case, I'd be curious what all else may have gotte= n 700-series call numbers before the 300-series took over UNIX docs.
<= div style=3D"font-family:Arial;font-size:14px;color:rgb(0,0,0)">
<= div style=3D"font-family:Arial;font-size:14px;color:rgb(0,0,0)">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 determine i= s that 301 series encompasses the original System V version documentation, = 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 Z= 8000, that's cool).

After System V gold, the wealth of UNIX documentation ap= pears to come from code 307-X instead, I'm assuming 307 is whatever per= mutation of USG/USL happened to exist at the time. However, there are a few= other codes that seem to sporadically be involved in UNIX docs as well as = other computing docs:

302 - Just a smattering of Writers Workbench docs, very hi= gh call number suffixes (950-958).

303 - Bunch of 3B20D (Real-Time-Reliable) doc= s as well as other 3B20 stuff, mainly hardware manuals but a few SVR2.1-rel= ated docs as well for 3B20A, S, and D

304 - Another smattering of 3B20 docs, thi= s time mostly A and S, mix of hardware and UNIX docs

305 - This one is hard to p= in down, they've got the basic 3B2 docs, some other guidance docs for n= on-20 3B computers, and a mishmash of language tools like assemblers, a BAS= IC interpreter, compilers, and a few odd technical bulletins for products c= overed in other groups

306 - There wasn't much direct UNIX documentation her= e, just stuff about 3BNet (3B computer networking?) and the 5620 DOT Mapped= terminal

308 - Documentation on a whole mess of software utilities with some od= d Sys V manuals sprinkled in. You've got stuff like the "Office Te= lesystem", Instructional Workbench, more docs on BASIC, Pascal, and CO= BOL, some Fortran stuff as well, and a few other reference documents
<= div style=3D"font-family:Arial;font-size:14px;color:rgb(0,0,0)">
<= div style=3D"font-family:Arial;font-size:14px;color:rgb(0,0,0)">310 - Seems= to be entirely related to Documenter's and Writer's Workbenches. W= hats odd is there is also a pretty even split of DWB and WWB documents in t= he 302 and 307 groups, so hard to say why the split, maybe a secondary depa= rtment producing supplementary literature? Very low call number suffixes, s= o possibly 302 transitioned into 310 for DWB/WWB support

311 - Might be a "= trade book" publishing arm, seems to only contain a few books, includi= ng "The C Programming Language"

320 - Might be the "standard syst= ems" trade books arm as opposed to the version/system specific documen= tation gotten from USL directly. This list contains books like the SVID, Ba= ch's Design of the UNIX Operating System book, some programming guidanc= e books, and the UNIX Programmer's Manual 5 volume series with the meta= llic alphabet blocks on the cover (echoing the V7 trade release). What'= s interesting is call number 320-X comes back around with SVR4 as the call = code that a number of 386-specific manuals were published 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, Programm= ing, and Support Tools guides, which curiously weren't published 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 e= arly SysV I wasn't aware of previously:

  • System V Gold= :
    • PDP-11
    • VAX-11<= /span>
    • 3B
    • M68000
    • Z8000
  • System V R2:
    • VAX-11
    • <= span style=3D"font-family:Arial">3B
    • M68000
    • NS32000
    • iAPX 286

It appears Bell also opted to have different documentation sets= for different processors in SVR2. We kinda see this later on with i386 var= iants of the SVR3 and SVR4 documents, but I don't think we ever quite s= ee 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 like that, bu= t a Release 5.3. I know I've seen "Release 5.2" listed in a f= ew places, which had me curious, is there a well established record of what= happened with internal (non research) UNIX after System V was branched? Wh= ether the development stream simply became System V development, or if ther= e was still a totally separate UNIX 5.x branch for a while that, while borr= owed into System V at necessary times, did still constitute a distinct bran= ch of development after the initial System V release. I know there is at le= ast 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 bein= g some more development work between CB and USG folks before they put the f= inal 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 num= bers from 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 project on= ce the rains start and I can't go play outside.

<= /div>
--0000000000002c012005ea6a53fc--