I thought it a rather droll remark and enjoyed it. The really awful result was mentioning this in the "Is it legal to hack a scope?" thread. It led to a flame war over the GPL & LGPL by people who didn't understand the language of the licenses and the context of American law.
I'm migrating a ZFS pool from 1 TB to 2 TB disks which is proving unspeakably slow, but I'm too far in to back up and use a different method. And most of my infrastructure is ripped up, sitting in a pile to be rebuilt. To top it off, starting Thursday I am going to be moving a 12' x12' x 34' cold room for my sister and her husband which I have only seen in photographs.
Much to my delight I took a moment to port scan the GDS-2072E and ssh is running on port 22
That was turned off in later releases, though I don't know which. But the root password is online somewhere. So extracting the working system is easy. It also makes turning it back on easy.
The real point of posting here is to try to enlist some help with tracking down information which is only of interest to GDS-2000E owners. All of that takes time. There are no magic wands. And I get *really* slow when I have to do complex things I haven't done before like hook up to the JTAG port. Moreover, no one has any advantage tracking down information via web searches. You *usually* can find it, but you can't say if it will take minutes or days.
A 1.25 million line package of stuff at a medium size oil company took me 6 weeks to get it to compile. And two of the three authors still worked there! They just did not have a firm grasp on what linker targets were where. So I'd go along until I hit something that wouldn't compile or link and go around asking them to look for the proper files and check them into RCS. A 500,000 line port from VMS to Unix took 6 months with 3 people working on it, though another contractor and I did most of the work and I built the build system and version control for it. That required locating and replacing all the VAX run time library calls. It took me 3 days to write and test the scripts that did that. I also wrote a scientific program that took over 1500 hours to write working alone and I did half the work on the weekends with a job in Houston, a house and dog in Dallas and an airplane ticket on Sunday and Thursday. Oh, and the job in Houston was *another* large pile of old code. I wore out the tee shirts a long time ago. About the only thing that would scare me would be building X11 and Motif from source again. That was my introduction to large scale software systems. The serpent on the cover of the Imake book is very apt.
Again, tl;dr, but I'm hoping to head off the "let's design open source HW" which is pointless because of the production issues and the "it's so complex it's impossible" which presumes that scopes are designed by God and handed down on the mountain.
My biggest concern is how and where to organize information and resources without running afoul of copyright law, etc.
Home
Help
Search
Login
Register
