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.'"
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'
http://www.theregister.co.uk/2001/04/12/missing_novell_server_discovered_after/
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.
"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.
From the linked thread: ... The only thing it's been connected to since 2004 has been my personal computer (laptop)."
"When I began work here in 2004, this system was completely orphaned
Way to spend (by my reckoning) 10,000 kWh of electricity.
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.
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
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!
Just to piss of pompous, holier-than-thou assholes like yourself. Mission accomplished!
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.
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