Slashdot Mirror


NetWare 3.12 Server Taken Down After 16 Years of Continuous Duty

An anonymous reader writes "Ars Technica's Peter Bright reports on a Netware 3.12 server that has been decommissioned after over 16 years of continuous operation. The plug was pulled when noise from the server's hard drives become intolerable. From the article: 'It's September 23, 1996. It's a Monday. The Macarena is pumping out of the office radio, mid-way through its 14 week run at the top of the Billboard Hot 100, doing little to improve the usual Monday gloom...Sixteen and a half years later, INTEL's hard disks—a pair of full height 5.25 inch 800 MB Quantum SCSI devices—are making some disconcerting noises from their bearings, and you're tired of the complaints. It's time to turn off the old warhorse.'"

18 of 187 comments (clear)

  1. Netware 3 by HornWumpus · · Score: 5, Interesting

    Netware 3 ruled.

    Netmare 2 on the other hand earned the name.

    By version 5 it was back to Netmare (for different reasons).

    I once walked into a dusty environment, remote location and could hear the drive bearings from 100 feet away through a fire door. Backed up successfully but never spun up again.

    --
    John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
    1. Re:Netware 3 by Anonymous Coward · · Score: 5, Interesting

      I doubt the drives were exactly 'up'. Spinning, yes.

      I had a legacy Netware 3.11 server once upon a time... it was up for years and years, and by the time I got to the company it was like a legend. Eventually though there was a power outtage that outstripped the UPS system and required a re-start.

      It wouldn't load. We sent the hard drives out to be recovered and they didn't actually exist anymore - the surface had been work away years before, and the server had been running purely in RAM.

      Netware was awesome.

    2. Re:Netware 3 by girlinatrainingbra · · Score: 4, Informative
      You can run Knoppix like this also, with everything stored in ram using the "to ram" command line option when booting up: knoppix lang=us toram no3d

      This works better for the CD-sized version of knoppix if you have only one-Gig of RAM, if you've got more than 6GB RAM, go ahead and use "toram" for the DVD-sized versions of Knoppix.

    3. Re:Netware 3 by cyberthanasis12 · · Score: 5, Interesting

      The thing that I liked most with netware 3.1* was the fantastic undelete it had. It never really erased anything unless it was out of storage. Once I remember I undeleted a file I had erased one month before. And the undelete was no hassle at all. You just looked at a list of the "erased" files and chose whichever you wanted. It's the only thing I (still) miss since I migrated to Linux in 1999.

    4. Re:Netware 3 by GovCheese · · Score: 4, Funny

      On the other side of an office door, I heard the worst noise I've ever heard from spinning drives and in my panic, didn't even see the "do not disturb" sign. Turns out it wasn't spinning drives I was hearing. The lactating woman on the other side of the door milking herself with a noisy pump nearly threw the infernal machine at me. Some things are not meant to be seen.

      --
      "He's using a quantum encryption scheme! That'll take hours to break!"
    5. Re:Netware 3 by HornWumpus · · Score: 4, Interesting

      Salvage was one of the best new features of Netware 3. That and not having to gen sys from 360K floppies.

      On netmare 2 the first thing you did when you got your first one up was put a copy of the install images on the share. Linking up (IIRC they called it genning sys) a copy of the server required you to feed it each of about 20 floppies three times each in apparently random order. Get one interrupt wrong and you get to start over (better to reset the interrupt jumpers to match the config you had).

      I should not remember any of this crap.

      --
      John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
    6. Re:Netware 3 by MavenW · · Score: 4, Interesting

      I got a call from an acquaintance who was a low level runner for a law firm. He asked if there was any way to resurrect files that had been deleted by a disgruntled employee who was laid off. She deleted a ton of important stuff. They didn't have any backups and were in a panic. I told him salvage might work, and explained how to get to it.

      He was a hero that day.

  2. Was it discovered in the wall?? by Anonymous Coward · · Score: 5, Funny
  3. Re:Is this supposed to be a good thing? by dreamchaser · · Score: 5, Insightful

    Netware 3.12 was quite secure and rock solid. It did one thing (file and print serving) very, very well. It's a testament to good software design. The fact that you make light of it probably indicates that you were not in the IT field back then and have no sense of perspective. I wasn't a huge Netware fan, being more of an OS/2 and Unix guy back in the day, but I had a great deal of respect for the product.

  4. Re:patch much by Anonymous Coward · · Score: 4, Insightful

    "My linux systems require constant patching for them not to be p0wned by script kiddies. Therefore it follows that every other system is the same.".

    Love that logic.

  5. Unused for the last 8 years by artbristol · · Score: 5, Informative

    From the linked thread:
    "When I began work here in 2004, this system was completely orphaned ... The only thing it's been connected to since 2004 has been my personal computer (laptop)."
    Way to spend (by my reckoning) 10,000 kWh of electricity.

    1. Re:Unused for the last 8 years by fnj · · Score: 4, Interesting

      Kids nowadays. No sense of adventure and wonder. Best use of 10,000 kWh ever.

  6. Re:patch much by The+Second+Horseman · · Score: 4, Informative

    Essentially - other than tunneling IPX over TCP/IP, which the site may or may not have been using - this version of Netware had no TCP/IP support. No web server, no nothing. Odds are this this wasn't much of a risk. My guess (the article didn't say) is that they were using it for something really specific.

  7. Re:patch much by 93+Escort+Wagon · · Score: 4, Insightful

    My guess (the article didn't say) is that they were using it for something really specific.

    It's pretty obvious the only thing they were using it for was to watch the runtime go up and up.

    The drive bearings had been noticeably failing for quite some time. The operators might pay some lip service as to why that somehow didn't matter, but the bottom line is - if the risk of a drive failure during operation isn't a problem, the machine isn't serving any real purpose.

    --
    #DeleteChrome
  8. Re:Time to go indeed by Bert64 · · Score: 4, Informative

    Once a drive starts failing like that, the worst thing you can do is reboot the box... The drive may continue running for years, but if you shut it off it may never be able to spin up again.
    Best thing is to get any important data off the drive without shutting it down.

    --
    http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  9. Re:16 years and they did not run of space on it? by Anonymous Coward · · Score: 5, Funny

    Just to piss of pompous, holier-than-thou assholes like yourself. Mission accomplished!

  10. Re:Seriously? by isorox · · Score: 4, Informative

    This was on Arstechnica like 3 days ago. This site is increasingly feeding on news carrion.

    This site has been doing that for years.

    There's still no other site with the quality of exta information you get from the comments.

  11. We ran an IPX-based public internet in the 90s by billstewart · · Score: 4, Informative

    IPX addresses had two parts - a 4-byte network number and a 6-byte host number that was almost always the MAC address. The network number was locally assigned, and in practice was almost always 00:00:00:00 (the default local network, because almost nobody actually bothered with routing), or FF:FF:FF:FF (broadcast), though some people got fancy and actually split up their networks into routed segments 1,2,3 etc. instead of bridging.

    So you could theoretically run an Internet-like network on it if there were some central authority assigning network numbers instead of everybody rolling their own, and it would scale better than IPv4 because there were 32 bits of network number!

    AT&T ran an IPX public internet in the mid/late 90s, in coordination with Novell. We assigned public network numbers, and sold connections. By now I've forgotten exactly what years it was, and I wasn't organizationally close enough to it to know if they actually got many customers, and of course there weren't really a lot of applications for it, but it probably ran for about two years.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks