Actually, what little of that show that I've seen makes me think I'd really hate it if I gave it a chance.
But this guy fits the profile.
Uncle Miod's machineroom
Sunday, September 16, 2012
Monday, June 18, 2012
Sunday, May 13, 2012
Now we're talking!
http://www.itworld.com/hardware/270936/living-computing-fossils-old-tech-holding-dear-life
Yeah, I remember those. First image after the kid's abacus is a plug-board. Never used them on the job, but we did cover them in school.
Yeah, I remember those. First image after the kid's abacus is a plug-board. Never used them on the job, but we did cover them in school.
Saturday, April 28, 2012
Penguicon
Penguicon http://penguicon.org
SF, computer geek stuff, and liquid nitrogen ice cream. If my wife was here it would be perfect.
SF, computer geek stuff, and liquid nitrogen ice cream. If my wife was here it would be perfect.
Saturday, March 31, 2012
From the Plan 9 World
One of the folks in the Plan 9 community has a blog, with some interesting perspective on the (now long-ago) Debian OpenSSH keygen bug.
http://research.swtch.com/openssl
Recommended, as is the entire blog.
http://research.swtch.com/openssl
Recommended, as is the entire blog.
Tuesday, March 20, 2012
If You Have Nothing Nice To Say
Start a blog
(3:12:18 PM) me: Junk mail from computerworld "What Your SAN Fabric Manager Isn't Telling You"
(3:12:23 PM) me: Like, I'm not using enough starch?
(3:12:34 PM) coworker: lol
(3:12:56 PM) me: I should so blog that. Haven't done anything in a while.
(3:12:18 PM) me: Junk mail from computerworld "What Your SAN Fabric Manager Isn't Telling You"
(3:12:23 PM) me: Like, I'm not using enough starch?
(3:12:34 PM) coworker: lol
(3:12:56 PM) me: I should so blog that. Haven't done anything in a while.
Saturday, January 28, 2012
Department of Redundancy Department
Found an old Redo Backup image of my ThinkPad on my external hard drive. Decided I wanted the space back, but didn't want to just delete it. (Pack rats point to me when they want to talk about people who hoard things.)
Didn't want to risk 'bit rot' on the DVD's I burned it too, so I ran Parchive to get Reed-Solomon error-correction files, then burned the Redo files and the *.par files to a set of disks.
But that's not being paranoid enough.
So, I ran DVDisaster on the ISOs that I'd built, then ran Parchive on the resulting ECC files, and made an ISO image from them. Then I re-ran DVDisaster on that ISO to include as much ECC data as would fit, and burned two copies.
So, if any of the primary DVD's bit-rot, the DVDisaster data should get them back. If not, I'll restore what I can, then use the PArchive files to get the Redo data back.
I have to admit, I didn't check to see if the Redo files and their Par files are spread out well enough that I can loose an entire DVD without being unable to recover.
Maybe I ought to burn another set...
(That direct link isn't responding right now, so here's the Wikipedia entry for Redo Backup)
Didn't want to risk 'bit rot' on the DVD's I burned it too, so I ran Parchive to get Reed-Solomon error-correction files, then burned the Redo files and the *.par files to a set of disks.
But that's not being paranoid enough.
So, I ran DVDisaster on the ISOs that I'd built, then ran Parchive on the resulting ECC files, and made an ISO image from them. Then I re-ran DVDisaster on that ISO to include as much ECC data as would fit, and burned two copies.
So, if any of the primary DVD's bit-rot, the DVDisaster data should get them back. If not, I'll restore what I can, then use the PArchive files to get the Redo data back.
I have to admit, I didn't check to see if the Redo files and their Par files are spread out well enough that I can loose an entire DVD without being unable to recover.
Maybe I ought to burn another set...
(That direct link isn't responding right now, so here's the Wikipedia entry for Redo Backup)
Thursday, January 12, 2012
Here's another sentence I never thought I'd read
From a recent Linux Weekly News summary of current Linux kernel development:
Normally I complain about how absurd such things would have been ten or twenty or whatever years ago.
This one seems absurd now.
For S390 users who find the current limit of 3.8TB of RAM to be constraining: 3.3 will add support for four-level page tables and an upper limit of 64TB (for now).
Normally I complain about how absurd such things would have been ten or twenty or whatever years ago.
This one seems absurd now.
Subscribe to:
Posts (Atom)