Slashdot Mirror


Join the Hunt For the Government's Oldest Computer (muckrock.com)

v3rgEz writes: As the saying goes, 'If it ain't broke, don't fix it.' If a machine is doing its job, reliably and without error, then common sense dictates that you just shouldn't mess with it. This is doubly true for computers and quadruply true for government computers. This lends itself to an obvious question: what's the government computer most in need of an upgrade? MuckRock has launched a new FOIA project to find out, and has already started receiving some interesting results.

28 of 147 comments (clear)

  1. The article has some interesting highlights by JoshuaZ · · Score: 2
    Some government agencies were much more responsive than others. Some of the responses are scary. From TFA:

    According to the FAA, just knowing what kinds of computers the FAA is using would endanger the security of national air traffic. That's pretty bad, both for this project and my confidence in our air traffic system.After all, despite my vague wording, the FAA found 11 pages of documents responsive to the same request. But! They refused to release any of their records to me, citing the blanket Exemption 3 because they deemed, "disclosure would be detrimental to the safety of persons traveling in air transportation."

    He does say in the article that some agencies have confirmed mainframes from circa 1970, but doesn't say which specifically. It should be interesting to see how this project goes over the next few months.

    1. Re:The article has some interesting highlights by bws111 · · Score: 3, Insightful

      It says he 'is catching wind' of circa 1970 computers. That is hardly 'confrmed'.

    2. Re:The article has some interesting highlights by Crashmarik · · Score: 3, Funny

      Well the FAA has the best security of any federal agency. You need to be an archaeologist to hack into their equipment.

  2. In-use vs owned/missing by Scoth · · Score: 4, Insightful

    I'd be curious if he has a way to differentiate active, in-use machines vs. old stuff that may just still be in the inventory roles. I helped a bit with my previous company's effort to clear out old storage and inventory and there was some pretty old equipment that had been in the closet for close to a decade, plus some stuff in their inventory records that had long since disappeared.

    So I wonder if that Gateway Liberty 2000 is actually still sitting on someone's desk where the toil away with WordPerfect and Windows 3.1 every day, or if it got tossed/walked out of the building in the late 90s and no one bothered to update the records.

    1. Re:In-use vs owned/missing by hey! · · Score: 2

      So I wonder if that Gateway Liberty 2000 is actually still sitting on someone's desk where the toil away with WordPerfect and Windows 3.1 every day, or if it got tossed/walked out of the building in the late 90s and no one bothered to update the records.

      j

      It might not be either. One thing I've frequently seen in government offices is really old software they don't have the funding or time to replace or update. So it's not necessarily being used every day, but it may get fired up a couple of times a month to run some old FoxPro database on Windows 3, or maybe even once a year to run a Lotus 1-2-3 spreadsheet that generates a report.

      If so the computer in question would be a good choice, because it's a small laptop. It wouldn't have to take up space on someone's desktop, you could shove it in a filing cabinet.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    2. Re:In-use vs owned/missing by DerekLyons · · Score: 3, Insightful

      So I wonder if that Gateway Liberty 2000 is actually still sitting on someone's desk where the toil away with WordPerfect and Windows 3.1 every day, or if it got tossed/walked out of the building in the late 90s and no one bothered to update the records.

      Or somebody set it on a shelf in case his 'new fangled' machine died and a backup was needed - and it's simply been handed down from one custodian to the next even since. Nobody cares that it's not needed and probably doesn't work anymore, the paperwork says we have it, and there it is on that self over there... and that's good enough.
       
      When I took over the department test equipment locker at TTF in the late 80's, I had a ton of stuff like that - old and obsolescent equipment squirreled away by previous custodians because "we might need it again some day". The bosses were OK with that because there was no penalty for having excess gear, and it was a massive pain in the ass to get rid of gear. (There's a lot of hoops to jump through to make sure that was in fact excess to requirements and that the person getting rid of it and his chain of command weren't simply trying to take it home themselves or sell it for their own profit or whatever.)

  3. Intredasting by Sax+Russell+5449D29A · · Score: 4, Interesting

    A couple of years ago I heard of a late-70's VAX still being used at a small power plant. To my knowledge it controlled some sort of HVAC systems. Another old system, one I've actually seen, was a mid-80's computer of unknown make/model used to control traffic lights in a small city. It's funny, or actually impressive, to see such old systems still in use. The old-school guys that keep them running tell nice stories about flea market and eBay scavenging.

    --
    -SR
    1. Re:Intredasting by sphealey · · Score: 5, Informative

      = = = A couple of years ago I heard of a late-70's VAX still being used at a small power plant. To my knowledge it controlled some sort of HVAC systems. Another old system, one I've actually seen, was a mid-80's computer of unknown make/model used to control traffic lights in a small city. It's funny, or actually impressive, to see such old systems still in use.= = =

      Those systems were designed to be reliable, maintainable, and understandable by thorough professionals, so it is in no way surprising they continue to work. And in the industrial infrastructure world you don't replace equipment just because there is a shinier new version. 50 year old equipment is not uncommon in the provision-of-electricity industry and I've seen some 80 year old stuff in operation.

      sPh

  4. If you think that's bad... by __aaclcg7560 · · Score: 3, Informative

    When a department gets downsized for one reason or another at my government job, the department manger is supposed to turn in all the unused workstations for redeployment or recycling. They typically don't. A favorite hiding space is the utility closet inside a women restroom. All the field techs are male. Go figure.

  5. waste of tax-payer's money to answer these by klindsay · · Score: 5, Insightful

    "If a machine is doing its job, reliably and without error, then common sense dictates that you just shouldn't mess with it."
    "what's the government computer most in need of an upgrade?"
    You've just given a great reason why some hardware is still in use, it works.
    Why turn around and conclude that it needs an upgrade?

    "knowing which agencies are running hardware older than I am is important"
    Sure, for a very loose definition of important.

    1. Re:waste of tax-payer's money to answer these by Teun · · Score: 2

      Except some, probably a lot, of them are hooked up to a network and the security status is as old as the HW.

      --
      "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
    2. Re:waste of tax-payer's money to answer these by tlambert · · Score: 3, Informative

      Meaning you don't have to worry about currently in use attacks, right?

  6. Re:Focus on NASA by __aaclcg7560 · · Score: 3, Informative

    What's with. the random periods. in your sentences?

    A double space on the iPhone virtual keyboard becomes a period. Type too fast, random periods appear.

  7. "If it ain't broke, don't fix it?" Fuck off. by imac.usr · · Score: 4, Insightful

    I hate that goddamn phrase. When the inevitable time comes when suddenly the old system *does* break, it's no longer under any support, nobody's left at the company who knows how it works, there's no budget for a modern replacement, and it has to be fixed in four hours or the company goes bankrupt. Been there, done that, ate the T-shirt after hours of working with no break for food.

    People who say "if it ain't broke, don't fix it" are the same idiots who brag about uptime.

    Pro tip: *every* system is broken. The trick is being able to repair or work around the broken parts without disruption, not to just seal it behind a wall and rediscover it years later when trying to track down what's still pinging.

    --
    I use Macs for work, Linux for education, and Windows for cardplaying.
    1. Re:"If it ain't broke, don't fix it?" Fuck off. by __aaclcg7560 · · Score: 3, Interesting

      Pro tip: *every* system is broken.

      Every system should be planned for. If a Windows 2003 Server is still on the network at my job, a planned exemption is on file to postpone removal for 30 days or gets pulled off the network. The server owner has six months to migrate to 2008 or 2012, but some people insist on dragging their feet and waiting until they have no choice. The process is somewhat easier these days as all the servers are virtualized across a server farm.

    2. Re:"If it ain't broke, don't fix it?" Fuck off. by Dutch+Gun · · Score: 5, Insightful

      The funny thing about pithy little phrases like that is that there's inevitably a counter-phrase that works to refute it. In this case, perhaps "don't put all your eggs in one basket" would be appropriate?

      There's nothing wrong with "if it ain't broke, don't fix it" as a general rule of thumb (nor of good uptime), but I'd certainly temper it with the notion that a lack of support or replacement parts can also be considered "broken", and thus in need of fixing. There's a lot of damage done by needless upgrades or "enhancements", which is what this phrase is meant to counter. I understand your frustration with idiots who view any one rule as some sort of golden rule handed down from on high, but... well, "don't throw the baby out with the bathwater."

      --
      Irony: Agile development has too much intertia to be abandoned now.
  8. Re:Focus on NASA by sphealey · · Score: 2

    Back in the 1980s my then-employer shared the cost with the FAA of updating IBM's 1401 emulator to the latest architecture (IIRC whatever was the half generation between 370 and 390), so I wouldn't count on that 360 being the oldest!

    sPh

  9. Footprints of old systems by T.E.D. · · Score: 4, Interesting

    I've found that sometimes old systems leave footprints that last far beyond the computers themselves.

    For example, a couple of years ago we had this working networked system that we wanted to upgrade one computer of. The issue was that the protocol used to talk between the systems was a custom network layer written on top of a serial protocol called DR-11W. The cards were rather hard to find, the hardware very finicky to get talking right, and finding good docs for our custom layer was a real challenge.

    I eventually found out in researching it that DR-11W was in fact the serial printer port on the original PDP-11's back in the 70's. Neither machine was a PDP-11, but since every upgrade ever done was one computer at a time, we've had to maintain this PDP-11 printer port communications interface for the last 40 years. The protocol even required converting all floating-point values to IBM's old format even though neither side used that format! The conversion's not trivial either.

    Our one vendor for these cards has since gone out of business. The story I heard is that they lost their building lease, and didn't feel like it was worth it to move. So it looks like next upgrade, the PDP-11 printer port networking may finally die.

    The moral here is that just because the 40-year-old computer may be physically gone, it might not really be gone.

    1. Re:Footprints of old systems by 93+Escort+Wagon · · Score: 2

      Ha! I remember having to do something along those lines back in the 1990s.

      The lab I worked at was running an early 1980s-vintage Micromass mass spectrometer (model 903, IIRC) We'd been paying through the nose for a maintenance contract on an HP 1000 computer, and finally I convinced my boss to let me move the machine control over to a PC (which we could buy for about three months' worth of HP maintenance payments). Well, one of the first things I found out was that Micromass used a serial protocol known as current loop - which, even then, was uncommon. Then, after I finally found a serial card that could handle current loop, I found out that Micromass had implemented it incorrectly. Fortunately, the protocol wasn't complicated, so I was able to physically modify that serial card to work with the mass spec (a much less daunting task back then, back before SoC and high density circuit boards were in everything). But for as long as that mass spec was still in use, that kludged card was necessary to keep the data flowing.

      --
      #DeleteChrome
    2. Re:Footprints of old systems by T.E.D. · · Score: 3

      I didn't say it was an IBM. I said our protocol uses IBM-format floats. I don't think the PDP-11's used that format, so that's probably the footprints of yet another old computer, long since upgraded.

    3. Re:Footprints of old systems by Lorens · · Score: 2

      In my office we have kept a box of punch cards. The program code names are written on the deck edge (which as a bonus served to check that the cards were in order -- I'll spare you the story about the off-site backup having a traffic accident). The people retiring nowadays tell us that they used punch cards when starting out, but it didn't last long, so in a few years no one in the office will have worked with punch cards . . . but programs with the very same code names still run on our mainframe. I haven't checked if they are identical to the punch card versions, but the code to work out things like the amount to pay every month on a thirty-year mortgage probably hasn't changed!

  10. You would (or wouldn't) be surprised... by mrbill · · Score: 4, Interesting

    I used to run a pair hobbyist/enthusiast sites for fans of DEC's VAX and PDP-11 series of machines.

    Shortly after 9/11, I got a phone call from someone at the Pentagon who was looking for certain parts so they could repair an older VAX that had been damaged in the attack. I was able to get them in touch with a third-party reseller who still had those bits in the back of a dusty warehouse.

    It was surprising that they hadn't upgraded to Alpha (which had been out almost ten years) then; the telco where I worked had one big system that had gone through three company changes (DEC -> Compaq -> HP) and had been upgraded in-chassis from VAX to Alpha.

    I think all large systems sold to the federal government are required to have service/support available for something like 5 to 10 years after final sale availability; can't find concrete details via Google.

  11. Not too surprising... by klubar · · Score: 4, Informative

    There are lots of systems that were designed around embedded PDP-8s and PDP-11s. And given the numbers of Digital VAX sold and specialized software it would not be very surprising if some of these systems are still be used. There were probably over 1.5 million of these machines sold (about 300,000 PDP-8s, 700,000 PDP-11s, 500,000 VAX machines), so there's probably some happily humming away.

    I'm sure the same is true for some earlier IBM 360/370, but they had a better upgrade path and were more expensive to start with. Most of those machines got replaced when they came off lease or the parts availability expired. But probably some of the software from the early 360's is still be used.

    Those were the days when machines were rock solid (and weighed about as much). Unlike today, when electronics are designed to be replaced every two years or so.

    1. Re:Not too surprising... by NicBenjamin · · Score: 3, Insightful

      In theory.

      In practice these tend to be used in arcane, highly technical settings, with fairly old workforces. Setting up a new system that does precisely what the old system does, including bugs that 60-something workers have figured out their way around, but not adding new bugs they won't be able to figure out their way around? Not cheap.

      Particularly since a) you can't pay any developer more then $174k (that's what Congresscritters make), and b) you still have to interface with the department across the hall which isn;t upgrading jack.

  12. Re: Focus on NASA by Type44Q · · Score: 3, Funny

    random periods appear

    "Scheduled monthlies" are bad enough; I can only imagine how rough "random" must be for those around you...

  13. The FAA doesn't really have systems from the 1970s by Chibi+Merrow · · Score: 2

    While we had fun telling visitors to the labs that most of systems running Air Traffic Control were "essentially from the 60s and 70s" that's only technically correct.

    The truth is the original HOST mainframes were replaced in the 80s, and then again in the 90s, and now being phased out for ERAM (which is built out of COTS PC parts). In some cases software was brought forward during upgrades, so it may have been possible you'd of been running some assembly code back from the Apollo era but not really. There were still some oddities, though (like the "units" of some fields being in 64ths of a nautical mile), that made interfacing with the ARTCC systems fun.

    There might be some ARTS IIA terminals left? Those are vintage early '80s, but I think they've all been replaced with at least IIE or IIIE ('90s) and are all slated to become some form of STARS (late '90s) by 2020 or so.

    --
    Maxim: People cannot follow directions.
    Increases in truth directly with the length of time spent explaining them
  14. Re:Nice way to waste taxpayer money by mschuyler · · Score: 2, Insightful

    Amen to that. The FOIA has a purpose--to maintain open government. It was not designed to allow the merely curious to indulge their historical fantasies. Replying to this kind of stuff costs money, and guess who pays?

    I've seen cases where, for example, an activist decides the local public library's stance on open access to the Internet violates their stance on "decency" because it allows some people to view pornography, so said activist embarked on a campaign to ask the library for EVERY document they had on budget, personnel, policies, emails, etc. It was so bad that the library--not exactly an over-funded and wasteful public agency, had to hire a full time secretary just to respond to the myriad of requests.

    Basically it all translated to less materials purchased and fewer service hours open to the public while taking an inordinate amount of the library management's time and resources.

    This is just harassment and a misuse of the statute enacted in good faith.

    --
    How about a moderation of -1 pedantic.
  15. Re:"If it ain't broke, don't fix it?" by AndyCanfield · · Score: 2

    Reminds me of my first marriage. One night, after twenty years, I discovered that it was indeed broke. A light tap, and the whole thing shattered. The most solid things are often the most fragile. It is wiser to periodically evaluate your universe.