You can buy amazing things for cheap from china, but you can't buy anything used or antique.
Although I suppose they'll get into copying ancient hardware if there's enough of a market.
In the meantime buy cheap stuff while you can. :)
If my replacement terminal works, I'm probably going to buy a few more. In fact ... I might even be able to build a small business out of grabbing old terminals off eBay and selling them back repurposed as Thinstations.
hm, repurposing.... reminds me of:
http://hackaday.com/2010/02/24/oscilloscope-doubles-as-a-serial-terminal/
It was all vector-based. Printing text through the interface was conceivably possible, but that would've been much more effort than the class required.
PDP Binder
whew. spellbinder, that sounds like a very sound 'it had to be proven' and having done that in your youth pro'lly makes you old and wise evil h4x0r.
I don't usually toot my own horn, but when I finished, it worked better than the reference controller built by the teaching assistant. :P
Spell
We've got a couple of digitizing oscilloscopes in our lab with LCD displays.
I daresay one of them may even have a touch-screen display.
Heck, even 10 years ago, we had digitizing oscilloscopes, but they were at least using a CRT to display the info. However, the trace was still digitized first and drawn on the screen via a normal video adapter. No direct-driving of the CRT guns by the signal being measured.
Certainly not as cool as the old green-screen o-scopes, but the digitizing scopes are a lot more advanced. With the digitizing scopes, the inputs can be very high-impedance, which means less distortion of the signal being measured.
It also means you can do a lot more signal analysis right on the scope instead of having to figure it all out by hand.
Oscilloscope Binder
connected, video out that can go to a projector... decodes all sorts of
digital signals...
nah. green sux. even paperwhite (which in the end was just bright green) sux. Amber rox da house.
/etc/X11/app_defaults/*XTerm-color :
*VT100*pointerColor: yellow
*VT100*cursorColor: yellow
*VT100*XtDefaultForeground: red
*VT100*foreground: orange
"Hmm, I think I should like to rip this Russian DVD (which I cannot even watch on my DVD player) to a video file on my computer."
It took longer to reboot into Ubuntu than it did to find and install an app and start making AVIs.
The windowlist applet started sticking to the wrong monitor.
I'd drag it back, it would stay for 1 second then pop back to the other/wrong monitor.
What the fuck I say. I started hunting around google but then thought the better of it, time to reboot.
So I did.
Then the really most fucked up thing happened. My vmware vms didn't start up, saying it required a driver recompile. Oh no not again. But wait. I never ever ever upgrade linux anymore for fear of that problem (really it's time I switch to vbox).
Then I notice that my mail only goes to september.
Something very not cool going on.
I look at df and get this: I'm booted on a raid-0 device
Real interesting since I blew away the drive and reinstalled a non-raid setup from scratch a while ago... like september.
Ahhh... I see the problem. BIOS booted off the wrong drive.
So I go to the bios and as I have to two identical drives, it's hard to tell which is the right one, but I switched to the other and voila I got my machine back.
I can't tell you the feeling of dread that goes through my stomach when I see my machine doesn't boot right.
So now I'm wondering how do I blow away the mbr on the second drive so it never boots again without killing the partition table?
You can use gparted and change the 'bootable' flag on the partion. But....shouldn't you edit the grub configuration instead?
So when it booted off that drive it came up in broken raid 0 mode and ran happily waiting for me to replace the first broken drive.
I have long since thought better of the idea and blew away the first drive and installed OS from scratch, but left second drive alone thus (as never occurred tome) it was still a viable functioning half of a raid 0 setup.
So I had a better idea. I invented raid minus 1.
Rather than have the OS manage live mirroring I decided to remove everything off the second drive and write a script to dd drive 1 to drive 2 once a week.
It's like raid 0 but not live. I have daily incremental backups to cover the span between dd script runs.
What I realized is that it's not just my data that's important, but the OS setup as well. I get such a sick feeling in my stomach when I realize I have no working machine and I have to do nothing but install configure install configure fight with vmware (which is really the worst of it) just so I can work from home and get my mail and such.
So my mirroring the drive once a week, if the first drive fails, I just change my bios and voila working machine, no installing of anything.
"BUT!" you say, "if you run dd on an active partition, it's not in any real state that should be backed up. It's a useless backup."
"NAY!" I retort.
I read an article a few years ago suggesting that you don't shut down your machine, you just power it off. Why wait for it to fuck around flushing buffers and what not, when really, the OS has so many layers of transaction log and whatnot, it generally can recover pretty well most of the time (esp ext 3 and ext 4) so really, if my live partition dd backup isn't usable it's a failing of ext4 not my backup mechanism.
Of course I haven't tried this out yet....