Slashdot Mirror
Build Your Own Blade Server
fw3 writes "Information week is reporting
that IBM and Intel are opening up the standards for the eServer BladeCenter. 'The companies will make available the design specifications for IBM's eServer BladeCenter product... hardware vendors can build "BladeCenter compatible" networking switches, blade adapter cards, and appliance and communications blades for enterprise networks.' Not really a new strategy for IBM, ISA of course was open from the start, IBM's technical references for the original PCs contained nearly all of the engineering data needed to build a PC. Looking further back I've been told by a reputable source that RCA was able to fully duplicate the System 360 System/360, mainframe working just a month behind IBM's own schedule by using IBM's published tech reports. (Of course IBM *didn't* share the details of OS/360, leaving RCA with a box but no OS.) See also stories from EETimes, CNN."
Try running your OS/360 programs on your brand new zSeries box. Apparently they'll run fine. Of course in the mid-80s (2 decades after OS/360 appeared) IBM pretty much owned the mainframe market and most serious jobs needed a mainframe, so I don't think OS/360 did too badly.
In soviet russia stale jokes recycle you!
where is the OS/360 today
It evolved into OS/370 than OS/390 (zSeries) and this line of systems is still sold today. Nice try but failing to sell the OS did not doom it to failure as your post implies.
Snowden and Manning are heroes.
Except for one of the key components to make a PC: the "Build your own BIOS" reference.
IBM included the BIOS source code in the technical references.
It had the entire friggin' BIOS listing!
The only reason we have the rights we have is that people just like us died to gain those rights. -- Cheerio Boy
The IBM PC-AT spec opened the door to the commodity "PC" industry. The spec was detailed, and useful, enough for cloners to copy the PC, and the power of competition to drive the vast deployment of cheap PC hardware worldwide. Spawning not only Microsoft and Linux, but the Internet as we (think we) know it today. Especially in light of the obstacles to innovation domino effect we have today, like business process patents, domain name squatting, and every other "legal engineering" trick, IBM's PC-AT spec publication was a work of technology heroism.
But of course, every silver lining has its cloud. For example, the PC-AT spec didn't specify exactly where the motherboard screw holes must appear. So not only were there incompatible motherboard/chassis combinations, but the kluges to accomodate the differences made many cheap boxes significantly more expensive for manufacturers on a volume basis. Just an example of how the 80% solution can spawn its own problems, that require 80% more time to solve. Let's hope we've learned from the last watershed spec publication, and get all the details in the new blade server specs. Especially if we're all going to use them.
--
make install -not war
or do, see for yourself
Actually OS/360 was "open source". In fact, it was never even copyrighted. I have the entire source on CD-ROM. Anybody can get it at http://www.cbttape.org.
OS/360 had two flavors. MFT and MVT. MVT became SVS when it had virtual storage added on. MVS was in parallel development and once stable replaced SVS. Again, virtual storage. MVS was replaced by MVS/XA when the addressing scheme was changed from 24 bit to 31 bit. MVS/XA was replaced by MVS/ESA along with changes in the I/O architecture. MVS/ESA was replaced by OS/390. OS/390 is in the process of being replaced by z/OS. z/OS is the "flagship" decendant of OS/360. Most programs written for OS/360 will still run on z/OS today. z/OS also has an integrated "UNIX" personality so that it is possible (but not easy) to port UNIX code to z/OS. I have done this with GNU make, gzip, and bzip2 myself. And I'm not an expert in C either! z/OS is fully 64 bit capable on the latest eServer zSeries mainframes. That's 64 bits of addressing and data in registers. At the same time it is fully backward with the older 31 and 24 bit address and 31 bit data registers.
Unfortunately, unlike the original OS/360, z/OS is almost 100% "closed" source. It is even written in a proprietary language with IBM does not license to the general public.
+4 interesting? More like -4 uninformative
/. these days. What the hell have htey done to deserve so much wrath?
Sun needs to read the writing on the wall, newspaper, toilet paper, everywhere * consumers are seeking alternatives from proprietary.
That is plain wrong. NFS isn't proprietry. SPARC is an ISO standard. Solaris runs on more than just SUN computers (ie Fujitsu ones as well, not mentioning Solaris/x86). As companies go, Sun is pretty un-proprietry and has been for quite a while.
Why is bashing Sun so fasionable on
SJW n. One who posts facts.
Troll? I was mis-informed. I knew that Compaq had to reverse-engineer the BIOS to make their PC's IBM compatible; I was not aware that they needed to do this despite the source code being available.
Mod parent overrated I agree. But troll?
The ways of gods are mysteriously indistinguishable from chance.
The programming group I worked for ordered a bunch of the original IBM PCs. They came with 160k floppy disk drives and 64k of RAM (upgraded from 16k). The included Technical Reference Manual included complete schematics for the system and I/O boards, plus a source listing of the BIOS. The only thing it didn't provide was a listing of the ROM BASIC, which was licensed from Microsoft.
IBM was following the example of Apple, who provided extensive documentation on the Apple II.
Mea navis aericumbens anguillis abundat
IBM's BIOS source was copyrighted. If Compaq had simply compiled the source code listing, they would have faced a lawsuit (and a unfriendly precedent in the form of Apple v. Franklin).
InfoWorld says the chassis and management module aren't open. So people can buy cheap blades... and still have to buy from IBM the box where to plug them.
Back in the mainframe days - which is when I got my start in the biz - OS/360 and OS/370 (up to OS/MVS V7) were open source. The source was distributed on microfiche, and system programmers were encouraged to modify the code to make the whole thing run better. There was a user organization called the Society to Help Avoid Redundant Effort (SHARE) at which system programmers shared their code modifications with each other, and with the IBM developers. Some of the good stuff made its way back into the standard "distro" - although we didn't call it that back then.
Similarly, the hardware diagrams were standard manuals that existed in every datacentre. I remember browsing through them shortly after I finished school (a hundred years ago or so) and thinking, "there really isn't much to these mainframe computers; nothing much more than the final exam in electronics." But based on those diagrams, and other info, our datacentre was the first in the world to put the 9th megabyte on an S 370/168!
And yes, at the time, I did get questioned about how on earth we could have so much work that we needed a 9th megabyte on a 168.