But can you tunnel wayland over ssh
This is needed for sanity.
995 publicly visible posts • joined 6 Jun 2015
There was a screen saver that took a snapshot of the screen and slowly random bits on the screen would drop down to the next non-white bit below. Eventually there was a set of pixels at the bottom of the screen where all of the bits came to rest.
Another screen saver took a snapshot of the screen and slowly caused the image to "melt" causing weird distortions of the screen.
It is interlisp. I used it for many years at Xerox as my desktop. It had mail, text editing, a couple of lisp structure editors, etc. in fact, everything you needed to get your work done. If it crashed (e.g., due to building power failure), when it came up all of your windows were just where you left them.
I still miss it (and Smalltalk 76).
When I taught computer science all of the students' submissions were run through a cheating detection program which gave a score between submissions. One term the checker flagged two of my students of having a very high degree of similarity, it was, in fact, the highest score that term.
So I printed out both submissions, did a diff (which showed nothing). I then looked closely at the two codes and noticed that the students were using a totally different approach. If they did copy code it would have been useless.
So I went back to the cheating checker output. It basically looked for syntactic similarities. Both students used a lot of System.out.println s for debugging and the cheating checker had matched them all up even though they were printing different things.
So I just threw everything in the trash and never mentioned it to the students involved.
Dartmouth created a time sharing system in 1964. It ran on a GE-225. It was later upgraded to a GE-235 which was three times faster and had more instructions. Of course the students used all of the extra instructions on the GE-235.
Since this was done on an NSF grant everything was public. Someone in GE got the idea of selling time sharing systems. So they got a GE-225 (and DN-30 etc.) and all of the source code. At which time they discovered that the code wouldn't run because of the use of GE-235 instructions. So they replaced the GE-225 with a GE-235 and put a wait loop in the executive to slow the machine down to GE-225 speeds. The code was labeled for exactly what it did. The customer was happy, GE was happy, and a lot of useless cycles were burned in the wait loop.
In the early days at college there was a planned power outage so we got a generator to run the studio. We then pulled the main breaker and made an extension cord with male plugs on both ends. one was plugged into the generator and the other into a convenient wall socket. Everything worked except the zip cord between the two plugs was quite warm to the touch. We had to be careful not to bunch up the zip cord to keep the temperature down. The generator was fueled with gasoline which we kept in glass jugs which we filled at the local gas station.
I'm glad OSHA wasn't around then.
Extra points: count the number of safety principles that were violated.
This was my strategy for paper documents. I would have several piles of papers, notes etc. in my office. I could remember which pile a document lived and using the principle of 1 inch per month allowed me to retrieve documents quickly.
The clean desk policy idiots didn't like this but, since they couldn't find anything in my office, I got a conditional pass.
I remember at the college where I taught, one of the professors moved a column vertically in a spread sheet and excel helpfully tracked all of the cell bindings to their new location.
When I did grading with a spread sheet I always added a perfect student. If this student didn't get 100% after all of the formula crunching I knew something was wrong.
Another true statement is: "You cannot communicate a ground reference faster than the speed of light."
If you are running signals a "long" distance you should also run the ground reference in the same direction in the same cable.
I used to run high-speed signals through ribbon cable grounding every other wire in the ribon. I used source termination (100 ohm resister in series with the source). The signal would divide in two at the transmitter end and send 1/2 the signal to the far end. Whereupon it was 100% reflected (making a full signal at the remote end). when the reflected signal got to the driver end it was 100% absorbed by the series resisters. This worked even though there might be multiple pulses in transit.
At the college I was attending, the police came to the computer center and said they found someone with several 9-track tapes and an incoherent story about them -- something about research or something. So we mounted the tapes and didn't find anything suspicious. Then we had a hard time convincing the police that it was perfectly normal for a computer scientist to have a load of tapes with a very confused story about them.
One day the college radio station went down. Sure enough a telephone repair man was in the basement disconnecting our wires to the transmitter. He was using an extremely old diagram and figured that the best way to proceed was to disconnect everything and then wire things up according to his outdated diagram. Physically pulling him away from the terminal block and reconnecting the stations wires fixed the problem.
We had a file server at Xerox that powered down when the building lost power. There was a good file scavenger program that could put all of the pieces together etc. Running it showed bad records in a spiral pattern across the disk. Evidently, the heads retracted while still writing!
(Backups restored everything.)
At the college I taught at we were studying permissions on files. Some student set the access pits to 000 on his user account and locked himself. Had to go to support to fix this.
Not really the students fault - he was just experimenting (as he probably should).
Lightning is a strange beast. A lot of it is RF. If you ground a lightning rod with a wire that makes a sharp turn, the lightning will go straight. The wire used to ground a lightning rod is a coarsely braided conductor more than an inch in diameter. All of the building gutters should be connected to the ground wires with a 1 inch wide copper strip. The actual ground to earth should be a 12 foot copper rod driven into the ground, preferably at three places around the house. The ground system should be wired to the electrical ground (that, by code, is a 6 foot galvanized pipe).
Remember, lightning rods attract lightning so you'd better be ready when lightning strikes.
What ever happened to LISP? It is fast, memory safe etc. and a pleasure to program in. A modern LISP has everything you need except acceptance. The newer programming languages haven't learned the lessons of LISP and reimplement everything in a buggy or limited way. The first LISP 1.5 is over 60 years old.
At college there was an early dollar bill changer. I figured it was there to be tested by the students. So I took a dollar bill, tied a string around it, and placed it in the machine and slid in the slide. A fierce tug-of-war ensued resulting in a shredded dollar bill and a dollar's worth of change. I then carefully arranged the shreds of the bill on the slide. It took the pieces and delivered another dollar's worth of change.
A year latter I saw another dollar bill changer so I roughed up the leading edge of the bill (a technique I learned to cause jams in IBM card readers) and shoved it in. It took the bill but didn't give any change. I complained and the person in charge opened up the machine and saw that the bill had jammed in the mechanism but didn't fall to a micro switch that would release the change. So I guess they learned something.
The original ethernet was 3 MBits and used black RG11U foam 75 ohm impedance (with 50 ohm connectors!) cables with vampire taps. The speed of propagation was 66% of the speed of light. The design of the cable interface to the vampire taps was done by Tat Lam as the PARC people weren't really analog hardware experts. The collision detect would not work on very high-speed networks because of the speed of light/propagation. Tests showed 99% utilization with an offered load of 300%. We had multiple protocols running on the net: pup, leaf sequin, paulos, xns, ip, breath of life etc. with some other protocols for playing TREK or mazewars.
Some of these protocols also existed on the ARPANET
Eventually we got a 10 MBit cable with 50 ohm impedance.
TCP/IP didn't have a field to indicate other protocols so we used an illegal length to indicate the other protocols.
The original ALTO computers had a hard-wired 8-bit address which had to be changed when changing nets to avoid duplicating some other machine on the net. I think that the maximum number of nets was 255. It was hard tracking down another machine with the same address. The best strategy was to check who just received an ALTO.
There was a road near a military base that used high-powered RADAR. The signal was strong enough to interfere with car's fuel injection electronics resulting in several stalled vehicles along this road. A business nearby with a pickup truck with a carburetor with no electronics made money towing these vehicles out of range of the RADAR.
Our car has automatic braking when on cruise control. It is not very smooth and sometimes when the car ahead changes out of my lane the system brakes anyway. If the car ahead slows down (smoothly) the system gets right behind the car and brakes suddenly.
Taking the car out of cruise control disables this feature.
It also beeps when backing up and a pedestrian walks around or a car sneaks up. This is good.
Mandating AEB might be good but the technology isn't quite there yet.
I used to work in a completely dark office with just the computer screen for illumination. One night I was working, the trash collector came around and flipped on the lights and screamed when she saw me. Since I am not a tidy person there were papers everywhere. She asked about this and I said that there was some sort of an explosion and she went away completely satisfied.
We were scientists and we had a reputation to uphold.
When I worked for Xerox I discovered a technique that would display anyone in the corporation's password in clear text. Even the CEO etc. A big hole in security. I sent the head of security his password with the code I used. It was for lazy PARC programmers that didn't like typing in their password all the time.
The head of Xerox security was asked if he changed his password (a long one etc.) and he said, "Why bother? Any new password would be just as vulnerable."
A year later this hack didn't work so I guess I had some effect in tightening security.
At Xerox the computer center ordered 100 magnetic tapes. Purchasing, without telling any one, ordered a different brand to save $1 a reel. These tapes could not be rewound once without clogging the magnetic tape reader to such an extent that the tape actually stopped in the tape reader. It took several demonstrations to prove that the tapes were worthless.
There was someone in the computer room back in the '60s who would pick up any IBM card from the floor and put it with the new cards. He also insisted that the printer software be changed to not slew a page after printing the user account number. Multiple errors resulted from his (non blank) IBM cards and all of the users learned to slew a page before printing.
I was at Xerox and used/maintained the 3 MBit ethernet cable. I never noticed much reflection from the tabs but did notice reflections from the cable connectors. The RG11U foam had a characteristic impedance of 75 ohms but the connectors were designed for a 50 ohm cable. The TDR I built could count connectors but barely nodiced the vampire taps. For a really long cable there were problems until I designed a bidirectional repeater which was placed in the middle of the long run.
In my opinion, Smalltalk-76 was the best Smalltalk. Peter Deutsch (sp?) did Smalltalk-78 and had a JIT compiler in it. Both had a special character set. Smalltalk-80 used ASCII and lost something. I wrote a microcoded floating-point for Smalltalk that sped floating point up by at least a factor of three. I also microcoded some commonly used methods.
Smalltalk-76 also had the best debugger I have ever seen. An error (generally "message not understood" resulted in a stack window. When expanded there were six panes. The top two were the stack trace window and a code pane with the piece of the code causing the error highlighted. You could click on any other stack frame to see the code and highlighted piece.
The next two windows showed the "class" variables with a window that could execute code in the class environment.
The last two windows showed the local variables with a window that could execute code in the local environment.
There were many options for restarting, continuing etc.
The class browser was a pleasure to use for examining code or writing code. You could modify anything, including "system" code.
The system was persistent so all of your windows etc. were restored when restarted.