TUHS September 2022

tuhs@tuhs.org

57 participants
31 discussions

Re: Re-implementations/Clean-Rooms et al.

by Clem Cole

On Thu, Sep 8, 2022 at 12:51 PM segaloco via TUHS <tuhs(a)tuhs.org> wrote: > Both Coherent and 4.4BSD have stuck out to me as examples of > not-quite-so-clean-room implementations that did well enough (more than > enough for BSD) and didn't die a fiery death in litigation (as much as USL > tried...). Be careful with that statement both parts of it are not wholly on target. In the first, AT&T chose not to litigate against Coherent fully. As was pointed out, Dennis and the team that examined the code base determined it was 'clean enough.' If I recall, his comment was something like "It was clear they had seen and had access to the AT&T IP at some point, most likely at University (IIRC many of the founders were ex-University Waterloo), but they did not find evidence of direct copying of files." BSDi/UCB *vs. *USL was a different kettle of fish altogether. As has been discussed here extensively (and needs not to be repeated), that suit was about *Trade Secrets and >>ideas<< that make up what we call UNIX.* The real interesting thing about that case is that had USL/AT&T won, the repercussions for the industry would have been way beyond just BSDi - *but all of the UNIX clones* and many of us on this list who had been "mentally contaminated" with AT&T's ideas (I still have my 'mental contamination' button somewhere in my archives). The good news is that the US courts had the good sense to realize that the moment the US Gov put the consent decree down in 1956 and required that AT&T make their IP available and then enabled AT&T had its people start to write about their work in the open literature (in UNIX's case the original CACM paper, but continuing with all the books, follow on papers, etc), plus being such wonderfully active participants in the research community at large, it could not be called a secret. > What I find interesting is that in this day and age, it seems there is > almost a requirement for true "clean-room" implementation if something is > going to be replicated, which I understand to mean the team developing the > new implementation can't be the same team that performed a detailed > analysis of the product being reimplemented, but the latter team can > produce a white paper/writeup/memorandum describing the results of their > analysis and the development team can then use that so long as it doesn't > contain any implementation details. > It's not "day and age" it's from the original case law -- the term was coined by the late Arthur Kahn, Esquire who was the lead attorney for Franklin Computers, Inc in the Franklin *vs.* Apple Case - which he originally won and ultimately lost on appeal [Good guy BTW, particularly for a non-technically trained person - he 'got it']. The concept is that one group is in a dirty room and the other in a clean room. Information is unidirectional. The dirty room can read published documentation, probe, and test the device/implementation using standard programming techniques. And then write a new document that describes the functionality of the device in question. Then hand it to the folks in the clean room who can reimplement a device to that new specification. The point of contention in the case is if *the original documentation for the device*, in this case, the Apple Assembler listing for Wos's Apple-II ROMs were protected by copy once they had been transformed from their printed form in Apple;'s red books into the binary and stored in the ROMS themselves. Franklin's 'dirty room' ultimately wrote a series of test programs that demonstrated each of the externally available locations and entries in the ROMs. This they documents and their new clean-room programmers wrote a new set of ROM that duplicated the functionality. IIRC the story is that Franklin ROMs were a few bytes smaller in the end. Compaq would later the same scheme for the IBM PC. > I would assume the current definition of a clean-room implementation only > requires that the developers/implementors don't have access to the code of > the parent product (source or reverse engineered), but could read manuals, > study behavior in-situ, and use that level of "reverse engineering" to > extract the design from the implementation, so not knowing the gritty > details, Coherent could be a true clean-room. > Be careful here. I used to work for a firm that did a lot of work for different vendors that would build some of these clean-room sub-systems (in fact for some of the folks -- at least one -- of the readers of this list). We were always careful for the clean-room people to be ones we were fairly sure had not seen that customers product previously. I was almost always on the 'dirty' team in many of those projects because I was so contaminated with the IP of so many of our customers' work. Because we worked for IBM, Sun, DEC, HP, DG, AT&T, *etc*. all at the same time had their IP in-house we had very strict rules about how things were handled. Even what sites and what sub-nets data could be on -- which system admins had the passwords. No one person had access to all of the passwords. We had a locked safe for each customer with secure things like passwords (really) and rooms with locks and videos, and access doors. It was really serious stuff. Frankly, I think part of why we got some of the "work for hires" tasks was because those firms trusted us to handle their IP properly. No way did we want to contaminate something accidentally. Some projects like our big TNC [Transparent Network Computing] system we were working on for all of IBM, DEC, HP, and Intel simultaneously -- 4 different teams. The architects could talk to each other, and we talked about common issues, but it was a different code. I know we implemented things a couple of times - although we got smarter. For instance, the original RPC marshaling was done for IBM with 'the awk script from hell' which later became an interface generator that all four teams used. > > BSD is a different beast, as they were literally replacing the AT&T source > code before their eyes, so there isn't much argument that can be made for > 4.4BSD being a "clean-room" implementation of UNIX. It was not a clean-room as Arthur defined it. It was rewritten over time, which replaced AT&T's implementation. Which is all that was ever claimed. > Given that, that's one of the more surprising things to me about 4.4BSD > prevailing in the lawsuit, because while Berkeley could easily prove that > they had replaced most of AT&T's code, there's still the fact that their > team did have complete and unfettered access to Bell UNIX code at least > circa 32V. I expect this is because you don't quite understand what happened. > but I remember reading somewhere that CSRG students and faculty avoided > commercial UNIX like the plague, Hmmm, I read it on the Internet -- it must be true ;-) CSRG had Ultrix/VAX, SunOS/3, and I believe HP-UX/PA sources. They shipped several DEC-developed drivers in 4.1A/4.1B/4.1C -- Sam, Bill Shanon, and I tested a couple of them on one of my machines in Cory Hall as DEC has donated one of the 3 CAD machines [UCBCAD - a.k.a. 'coke' ], and it was the only 'pure' DEC machine on campus - without any 3rd party HW in it. After I graduated, I suspect Sam continued the relationship with Tom Quarles, so 4.2BSD was likely tested on that system too. But I know the RH-based TAPES and DISKs were all straight from Shannon's SCCS Ultrix repo as he sent them to me to try before I gave them to Sam. > Does anyone know if there was a "formal" PDP-11 and/or VAX disassembler > produced by Bell? Most of the compiler kits have disassemblers, as do many debuggers -- what are you asking? > saying something to the effect "Rumor has it there is a PDP-11 > disassembler" but I'm curious if such tools were ever provided in any sort > of official capacity. > In the mid/late-70s (*i.e.* V6/V7 time frame) there are a couple of them -- where to start -- V7 has one inside of adb, and if I recall later versions of PCC2 has one. But if you look in the USENIX tapes you can find a couple of pretty well-adorned ones. There was one that IIRC was done by ??Cooper Union?? guys that spit out DEC MACRO-11 syntax for the Harvard assembler. That should be on the TUHS archives. Thinking about it, Phil Karn had one too that did some interesting label patch-up IIRC - which I think he brought with him to CMU from somewhere -- but I may be miss remembering that.

2 years, 3 months

"... interesting old-timey UNIXes ..." (cross post from geeks)

by Grant Taylor

Hi, The following comment was made on the geeks mailing list and I figured it was worth cross posting to the TUHS mailing list. -- I'm BCCing the original poster so that they are aware of the cross post and in case they want to say more. --8<-- In related news that might entertain and inform, there are some interesting old-timey UNIXes out there that I've come across recently though: XV6: https://pdos.csail.mit.edu/6.828/2012/xv6.html OMU: http://www.pix.net/mirrored/discordia.org.uk/~steve/omu.html V7/x86: https://www.nordier.com/ RUnix and Singlix: https://www.singlix.com/runix/ -->8-- I don't know if any of it should be included in the TUHS archives or not. -- I figure discussing it on TUHS is the best way to find out. P.S. Re-sending to the correct TUHS email address. Somehow I had something on file reflecting the old server. :-/ -- Grant. . . . unix || die

2 years, 3 months

Re: Does anybody know the etymology of the term "word" as in collection of bits?

by jnc＠mercury.lcs.mit.edu

> It was used, in the modern sense, in "Planning a Computer System", > Buchholz,1962. Also in the IBM "650 Manual of Operation", June, 1955. (Before I was born! :-) Noel

2 years, 3 months

Re: Does anybody know the etymology of the term "word" as in collection of bits

by jnc＠mercury.lcs.mit.edu

> On Sep 8, 2022, at 9:51 AM, Jon Steinhart <jon(a)fourwinds.com> wrote: > One of those questions for which there is no search engine incantation. Whatever it is, it's really old. I found it used, not quite in the modern sense, in "Hi-Speed Computing Devices", by ERA, 1950. It was used, in the modern sense, in "Planning a Computer System", Buchholz,1962. Noel

2 years, 3 months

Re: Has this been discussed on-list? How Unix changed Software.

by Douglas McIlroy

> (Research) Unix ... 'shipped' with zero known bugs. It wasn't a Utopia. Right from the start man pages reported BUGS, though many were infelicities, not implementation errors. Dennis once ran a demo of a ubiquitous bug: buffer overflow. He fed a 2000-character line on stdin to every program in /bin. Many crashed. Nobody was surprised; and nobody was moved to fix the offenders. The misdesign principle that "no real-life input looks like that" fell into disrepute, but the bad stuff lived on. Some years down the road a paper appeared (in CACM?) that repeated Dennis's exercise. > An emergent property is "Good Security” Actually security (or at least securability) was a conscious theme from the start to which Ken, Bob Morris, and Fred Grampp gave serious attention. Networking brought insecurity, especially to Berkeley Unix. But research was not immune; remote execution via uucp caused much angst, but not enough to kill it. In regards to the basic question. To oversimplify: Theme 1. Unix facilities encouraged what Brian recognized and proselytized as software tools. Theme 2. OS portability was new and extraordinarily final. Subsequent OS's were all portable and were all Unix. Doug

2 years, 3 months

Does anybody know the etymology of the term "word" as in collection of bits?

by Jon Steinhart

One of those questions for which there is no search engine incantation. Jon

2 years, 3 months

"dmd-pgmg" Toolchest package (SysV 5620+630 version of Sam)

by Mike Haertel

Does anybody out there have a copy of the old AT&T Toolchest "dmd-pgmg" package? This apparently includes the a SysV port of Sam for 5620/630 as well as other programs for the AT&T windowing terminals.

2 years, 3 months

Has this been discussed on-list? How Unix changed Software.

by steve jenkin

I’ve been looking at this question for a time and thought it could’ve appeared on the TUHS list - but don’t have an idea of the search terms to use on the list. Perhaps someone suggest some to me. As a starting point, below is what John Lions wrote on a similar topic in 1978. Conspicuously, “Security” is missing, though “Reliability & Maintenance” would encompass the idea. With hindsight, I’d suggest (Research) Unix took a very strong stance on “Technical Debt” - it was small, clean & efficient, even elegant. And ‘shipped' with zero known bugs. It didn’t just bring the Unix kernel to many architectures, the same tools were applied to create what we now call “Open Source” in User land: - Multi-platform / portable - the very act of porting software to diverse architectures uncovered new classes of bugs and implicit assumptions. Big- & Little-endian were irrelevant or unknown Before Unix. - full source - compatibility layers via - written in common, well-known, well-supported languages [ solving the maintenance & update problem ] - standard, portable “toolchains” - shell, make, compiler, library tools for system linker, documentation & doc reading tools - distribution systems including test builds, issue / fault reporting & tracking An emergent property is "Good Security”, both by Design and by (mostly) error-free implementations. In the Epoch Before Unix (which started when exactly?), there was a lot of Shared Software, but very little that could be mechanically ported to another architecture. Tools like QED and ROFF were reimplemented on multiple platforms, not ‘ported’ in current lingo. There are still large, complex FORTRAN libraries shared as source. There’s an important distinction between “Open” and “Free” : cost & availability. We’ve gone on to have broadband near universally available with easy to use Internet collaboration tools - e.g. “git”, “mercurial” and “Subversion” just as CVS’s. The Unix-created Open Source concept broke Vendor Lock-in & erased most “Silos”. The BSD TCP/IP stack, and Berkeley sockets library, were sponsored by DARPA, and made freely available to vendors as source code. Similarly, important tools for SMTP and DNS were freely available as Source Code, both speeding the implementation of Internet services and providing “out of the box” protocol / function compatibility. The best tools, or even just adequate, became only a download & install away for all coding shops, showing up a lot of poor code developed by in-house “experts” and radically trimming many project schedules. While the Unix “Software Tools” approach - mediated by the STDOUT / STDIN interface, not API’s - was new & radical, and for many classes of problems, provided a definitive solution, I’d not include it in a list of “Open Source” features. It assumes a “command line” and process pipelines, which aren’t relevant to very large post-Unix program classes: Graphical Apps and Web / Internet services. regards steve jenkin ============== Lions, J., "An operating system case study" ACM SIGOPS Operating Systems Review, July 1978, ACM SIGOPS Oper. Syst. Rev. 12(3): 46-53 (1978) 2. Some Comments on UNIX ------------------------ There is no space here to describe the technical features of UNIX in detail (see Ritchie and Thompson, 1974 ; also Kernighan and Plauger, 1976), nor to document its performance characteristics, which we have found to be very satisfactory. The following general comments do bear upon the present discussion: (a) Cost. UNIX is distributed for "academic and educational purposes" to educational institutions by the Western Electric Company for only a nominal fee, and may be implemented effectively on hardware configurations costing less than $50,000. (b) Reliability and Maintenance. Since no support of any kind is provided by Western Electric, each installation is potentially on its own for software maintenance. UNIX would not have prospered if it were not almost completely error-free and easy to use. There are few disappointments and no unpleasant surprises. (c) Conciseness. The PDP-11 architecture places a strong limitation on the size of the resident operating system nucleus. As Ritchie and Thompson (1974) observe, "the size constraint has encouraged not only economy but a certain elegance of design". The nucleus provides support services and basic management of processes, files and other resources. Many important system functions are carried out by utility programs. Perhaps the most important of these is the command language interpreter, known as the "shell". (Modification of this program could alter, even drastically, the interface between the system and the user.) (d) Source Code. UNIX is written almost entirely in a high level language called "C" which is derived from BCPL and which is well matched to the PDP-11. It provides record and pointer types, has well developed control structures, and is consistent with modern ideas on structured Programming. (For the curious, the paper by Kernighan (1975) indirectly indicates the flavour of "C" and exemplifies one type of utility program contained in UNIX.) Something less than i0,000 lines of code are needed to describe the resident nucleus. pg 47 (e) Amenability. Changes can be made to UNIX with little difficulty. A new system can be instituted by recompiling one or more files (at an average of 20 to 30 seconds per file), relinking the file containing the nucleus (another 30 seconds or so), and rebooting using the new file. In simple cases the whole process need take no more than a few minutes. (f) Intrinsic Interest. UNIX contains a number of features which make it interesting in its own right: the run-time support for the general tree structured file system is particularly efficient; the use of a reserved set of file names smooths the concepts of device independence; multiple processes (three or four per user is average) are used in a way which in most systems is regarded as totally extravagant (this leads to considerable simplification of the system/user interface); and the interactive intent of the system has resulted in an unusually rich set of text editing and formatting programs. (g) Limitations. There are few limitations which are of concern to us. The PDP-11 architecture limits program size, and this for example frustrated an initial attempt to transfer Pascal P onto the 11/40. Perhaps the greatest weakness of UNIX as it is presently distributed (and this is not fundamental!) is in the area where other systems usually claim to be strong: support for "bread and butter" items such as Fortran and Basic. (h) Documentation. The entire official UNIX documentation, including tutorial material, runs to less than 500 pages. By some standards this is incredibly meagre, but it does mean that student can carry his own copy in his brief case. Features of the documentation include: - an unconventional arrangement of material (unsettling at first, but really very convenient); - a terse, enigmatic style, with much information conveyed by innuendo; - a permuted KWIC index. Most importantly perhaps UNIX encourages the programmer to document his work. There is a very full set of programs for editing and formatting text. The extent to which this has been developed can be gauged from the paper by Kernighan and Cherry (1975). ============== -- 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

2 years, 3 months

Re: Has this been discussed on-list? How Unix changed Software.

by Douglas McIlroy

>> a paper appeared (in CACM?) that repeated Dennis's exercise. > Maybe this one? > B.P. Miller, L. Fredriksen, and B. So, "An Empirical Study of the Reliability > of UNIX Utilities", Communications of the ACM 33, 12 (December 1990). > http://www.paradyn.org/papers/fuzz.pdf Probably. I had forgotten that the later effort was considerably more elaborate than Dennis's. It created multiple random inputs that might stumble on other things besides buffer overflow. I see a Unix parable in the remarkable efficacy of Dennis's single-shot test. Doug

2 years, 3 months

i386 binary of 4.4BSD-Alpha

by MOCHIDA Shuji

I added i386 binary compiled from 4.4BSD-Alpha source. http://www.netside.co.jp/~mochid/comp/bsd44-build/ Boot with bochs works rather well. qemu-system-i386 also boots, and NIC (NE2000 ne0) works good, but kernel prints many "ISA strayintr" messages. I got many useful infomations from below 2 sites: "Fun with virtualization" https://virtuallyfun.com/ 386bsd bochs qemu "Computer History Wiki!" https://gunkies.org/wiki/Main_Page Installing 386BSD on BOCHS First time, I tried to compile i386 using 4.4BSD final (1995) source, patching many many pieces from 386BSD, NetBSD, and else.. but then, I felt "Well, we have BSD/OS 2.0, NetBSD 1.0, and FreeBSD 2.0 those are full of good improvements.." So, I changed target, and remebered Pace Willisson's memo in 4.4BSD (and in 4.4BSD-Lite2 also) sys/i386/i386/README: "4.4BSD-alpha 80386/80486 Status" June 20, 1992 that file says "can be compiled into a fairly usable system". yeah, needed chages not so small, though. -mochid

2 years, 3 months

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 September 2022