Lauren Weinstein2d ago

There are basically two ways to look at the fact that we're still using many of the same command line tools today that originated on UNIX of around half a century ago:

1) Serious stagnation
2) Ken and Dennis and the rest of the gang in the Bell Labs MH1127 lab, etc. got it right

L

Show threadMatt Panaro
@lauren the longer I live (and the existence of the Unix Hater's Handbook aside), the more I believe in 2
Mar 20 at 3:50pmWeb
Show threadPeter Ludemann2d ago

@eigen @lauren The Unix Haters Handbook is mostly the X11 and csh haters handbook. And nobody has bothered to do a Windows Haters Handbook (or VMS or z/OS).

Although there are some less than ideal parts of Unix, many of which were fixed in Plan9. And cdecl is a lifesaver whenever I'm writing C.

Show threadLauren Weinstein2d ago

@PeterLudemann @eigen No JCL Haters Handbook either AFAIK. And yeah, JCL is still in use.

//SYSIN DD DUMMY

Show threadPeter Ludemann2d ago
@lauren @eigen Despite REXX being able to do anything that JCL does (and much much more). I still have nightmares about the thousands of lines of assembler I wrote to work around deficiencies in OS/370 and JCL (if you have C code that runs on mainframes and opens files by name (instead of by ddname), you can thank me).
Show threadLauren Weinstein2d ago
@PeterLudemann @eigen I never needed to work in the 370 ecosystem, but I dealt with the 360/91 ecosystem at UCLA in parallel with my work on UNIX in the ARPANET lab. Of course most people on campus had no idea the latter existed, and given sentiments at the time we didn't really advertise that DOD effort. During the period I was at RAND they primarily used a 370, but I didn't have much direct interaction with that since I was running the UNIX 11's in the basement that serviced the information sciences folks. However, on that day at RAND when one of the 11's started filling my machine room with smoke and I pressed The Big Red Button That Is Never To Be Pressed, that instantly took down everything in my machine room (including the ARPANET IMP/TIP in there) and apparently some of the 370 drives that were in an adjacent basement room, so the 370 team was definitely interested in that. Management was actually pleased I acted when I did, since apparently if I had been even a few seconds later the Halon would have fired and that would have been a real mess.
Show threadPeter Ludemann2d ago
@lauren
The university mainframe had some PDP-11 frontend communication controllers (the less said about IBM's 3705, the better). One day, the DEC repairman came in to fix one of the PDP-11s, hooked up his oscilloscope, and the mainframe went dark. It turned out that there was a floating ground and when the oscilloscope was used, it connected the floating ground to the real ground and blew the fuses (and some other things - there was probably smoke from the oscilloscope and/or the PDP-11).
@eigen
Show threadLauren Weinstein2d ago
@PeterLudemann @eigen So at RAND one day I figured out that some random crashes of one of the two 11s (very upsetting to the users and making a lot of work for me to fix things in that pre-fsck era), was due to static discharge. Under certain conditions, just touching the control panel could do it. I told my manager and he didn't believe me. He came down to the machine room and told me to "prove it". So I did.