Some products "require" 64bit (e.g. Informix as per our DB group). And if many products are not supported in 64bit, are we doomed to maintaining two flavors (plus SLES8, SLES9) of z/linux? Which should be the default -- 31bit, unless a particular product requires 64bit, perhaps?
More and more, our security group demands that we apply the latest security patches, so more than machine performance, I more concerned about human labor requirement issues. Ismael Ifurung -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Peter Webb, Toronto Transit Commission Sent: Wednesday, March 30, 2005 10:01 AM To: [email protected] Subject: Re: zLinux 31 to 64 bit My understanding is that many products are not supported on 64 bit, so there is a problem right there. I also have the impression that 64 bit z/Linux is not quite as polished as 31 bit. Quite aside from that, most applications don't need 64 bit. Linux is not like another operating system where you will be cast into purgatory if you don't upgrade NOW. If the application is happy on an older release, why invite trouble by moving it to a new release? Unless of course the new release has something that you want/need. Products can take awhile to be certified for a new Linux release, so that is another disincentive to rush into an upgrade. Labra lege -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Tom Duerbusch Sent: March 30, 2005 12:22 To: [email protected] Subject: Re: zLinux 31 to 64 bit Well, I've read the manual, and basically, the only question that I asked that it answered was that to use 64 bit Sles9, you have to do a new install. But considering the lack of response from others, it kind of leads me to believe that anyone that is going to Sles9 and has earlier releases of Suse, are not migrating their applications to the next release. No matter what, I'll convert the Sles7 images to Sles9. The question is why or why not would someone convert Sles8 images to Sles9 and whether to convert Sles9 31 bit to Sles9 64 bit. So, is it a given that everyone should do the conversion? Or that you shouldn't do the conversion? That is given, that is it not a problem from the application side to do the conversion? Tom Duerbusch THD Consulting >>> [EMAIL PROTECTED] 03/29/05 12:28 PM >>> Some answers to your questions are in a "Linux 2.4 to 2.6 Transition Guide" PDF mentioned in today's posting by Jim Sibley: " Linux on zSeries page http://www-1.ibm.com/servers/eserver/zseries/os/linux/index.html There are more and more links to whitepapers, tips and hints, redbooks (and of course, marketing stuff). An interesting white paper is available there dated this month (March,2005): Linux 2.4 to 2.6 Transition Guide. Jim Sibley" -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Tom Duerbusch Sent: Tuesday, March 29, 2005 1:25 PM To: [email protected] Subject: zLinux 31 to 64 bit Soon, we will have a z/890 and I need to make, at least, some of my Linux images, 64 bit. At that point, we will be on z/VM 5.1. 1. At this point, I don't really have a problem with just reinstalling Sles9 in order to get 64 bit. However, is there a way to migrate or toggle 64 bit mode in a Sles9 image installed on a 31 bit system? 2. I have some Sles7 and Sles8 images that I was thinking of reinstalling as Sles9 images. They don't need 64 bit capabilities. Is there a reason to install Sles9 as 31 bit when you have a 64 bit environment? Is there a performance hit on 64 bit vs 31 bit? Can you install a 31 bit Suse9 when in a 64 bit environment? 3. Sles9 seems to take more resources with the default install then Sles8 and Sles7. A Sles9 31 bit image would use swap space when booting with 32MBs, vs Sles7 and Sles8 never used swap during boot even in a 24MB machine. Others have indicated that Sles9 seems to take more CPU when idling. It seems to me that there are more services running by default in Sles9 that need to be looked at and/or shutdown. Getting off of Sles7 is a given. Too old and I don't want to have the administraction overhead of supporting every Suse version<G>. But what are others feeling of having mixed release levels of Suse, given an environment where you don't have to. i.e. it is easy to migrate Sles8 to Sles9? 1. Why bother? 2. Yea, I'll get to it later? 3. Bite the bullet and stop supporting mixed environments? 4. Wish we could do it? 5. Don't, stop! The additional resources is a concern? 6. I don't like change? (hey, I still have my VM/ESA 370 mode packs spinning...don't ask) 7. We migrate when we need to. 8. The release dies when the application dies (or a new release needs to be installed). Any other migration issues sites on Sles9 have? Thanks Tom Duerbusch THD Consulting ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon, this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error, please contact the sender and delete the material from any computer. The integrity and security of this message cannot by guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail, or for the consequences of any actions taken on basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property of the TTC and must not be altered or circumvented in any manner. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
