IBM has adopted a number of OS(s) to run on its hardware. 1) IBM's MVS which is now call OS/390 2) IBM's UNIX which is called AIX 3) Red Hat's Linux 4) IBM's OS/2 5) There are no doubt many more.
There are many OS choices when it come to IBM. I think IBM will definite put its stamp on Red Hat's Linux, but whether IBM will replace Red Hat's RPM, (eg RedHat's Package Management), with something along the lines of IBM's SNP seem doubtful to me. The most basic feature of Linux, (eg the kernel), will continue to be controlled by the Open Source Community under the Open Source License. Since there are many different distributors of Linux with each distributor having their own package management application, its not clear to me how IBM could influence Linux package management as a whole, since IBM has partnered with Redhat to run its distribution of Linux on IBM hardware. I do think IBM will have a definite influence on Redhat's distribution of Linux for the IBM 390 and z series mainframes, though. You can find more information on this subject by doing a google on "Linux on IBM Mainframe". Below is an article you will enjoy. http://linuxlookup.com/2007/may/09/ibm_and_red_hat_announce_worldwide_enterprise_linux_on_mainframe_program or http://tinyurl.com/yq9ybc Regards, LelandJ Bill Arnold wrote: > Leland, I can't, quickly anyway, seem to locate an overview, but one of > IBM's redbooks describes SMP with a few words: > > "Chapter 3 describes OS/390 SMP/E which is a tool designed to manage the > installation of software products on your OS/390 system and to track the > modifications you make to those products." > http://www.redbooks.ibm.com/abstracts/SG245653.html?Open > > Substitute "Linux" for "OS/390" in the above, is what I'm saying. Not > impossible. IBM has done this with z/OS > http://www-306.ibm.com/common/ssi/rep_ca/7/897/ENUS201-257/index.html > > Here's a book that describes the rules for packaging products and > maintenance for MVS using SMP > http://publibz.boulder.ibm.com/epubs/pdf/gim25x00.pdf > > That that I'm saying anyone should read these specific rules, because > it's for a specific OS, but to point out that such a reference does > exist and that one can be made for Linux as well. > > This approach to product packaging, delivery, installation and > maintenance has served IBM very well over the years, and it's something > that can work to our great advantage (unless we like dealing with > solving compatibility problems) if it works out this way. > > And the whole thing can be automated, fed over the net (as the 2nd > reference above talks about, for z/OS). > > > Bill > > > >> IBM in the past had used red hat Linux for its smaller >> clients and SUSE >> Linux to run with the big dogs. IBM upgraded SUSE Linux >> security to run >> on its mainframe computers (eg the 390 I think). >> >> Now that Microsoft has signed an agreement with Novell, who own SUSE >> Linux, to partner in allowing Microsoft to offer SUSE Linux to its >> clients and to improve interoperability between Linux and >> Window, IBM is >> now going with a stronger relationship with Red Hat, and will use Red >> Hat on its mainframe computers. >> >> Both Red Hat and SUSE Linux are commercial product that are offered >> under a license that includes support, but other >> non-commercial version >> of Linux do a heck of a job of keeping their products patch >> and up to date. >> >> Most ides and languages running on Linux are OS agnostic. >> Going with an >> ide and language that is OS agnostic has its advantages. Many open >> source languages are both OS agnostic and free. This avoid the >> Microsoft or other vendor lock-in that could cost big buck to the >> clueless over the long haul. >> >> Anyway, its a great time to be involved with developing web based >> applications using tools like the Komodo ide, perl, php, >> python, ruby, >> and java languages, the eclipse ide, the netbeans ide, etc. Once an >> application is developed, you offer it to your client base or >> otherwise >> market it, and then place it on computers that are hosted by IP (eg >> Internet Provider). The hosting providers receive income >> from providing >> hosting services and doing all the IP stuff like keeping the hardware >> running and applications backed up, and the application developer >> receive income from licensing the software, installing it on >> the hosting >> provider, and maintaining/updating the application. >> >> Regards, >> >> LelandJ >> > > > [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
