Re: Time Zone problem
-Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Stahr, Lea Sent: Monday, January 08, 2007 11:23 AM To: LINUX-390@VM.MARIST.EDU Subject: Time Zone problem I have what I think is a major Linux problem (not on s390 of course). I have a large Red Hat 8 cluster. I have searched the Red Hat database and found the Time Zone patch https://rhn.redhat.com/errata/RHEA-2006-0745.html but it does not list a RH8 version. Any ideas? I have the patch for SuSE already and am installing that already on my 15 systems. I found the RHEL3 patch listed also that I need. You might consider the following: (credit to http://www.twinsun.com/tz/tz-link.htm) 1. Pull the current tzdata file from ftp://elsie.nci.nih.gov/pub/ 2. Expand the tzdata2007a.tar.gz file into a directory 3. Run zic against each time zone file of interest, such as: zic northamerica zic africa zic australasia zic europe .. zic pacificnew 4. Steps 1-3 will update the Olson database at /usr/share/zoneinfo 5. Don't forget to update /etc/localtime with the correct *new* zone info file. Perhaps the best way to do this is the setup command in RH8 and select the correct time zone again. If not, then make a copy of the appropriate TZ file. For me, I did: cp /usr/share/zoneinfo/CST6CDT /etc/localtime I believe the above will make your old RH systems up-to-date at the OS level for the new time zone change. No guarantees and criticism welcome :) David Schaub -- 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. If the reader of this message is not the intended recipient, you are hereby notified that your access is unauthorized, and any review, dissemination, distribution or copying of this message including any attachments is strictly prohibited. If you are not the intended recipient, please contact the sender and delete the material from any computer. -- 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
Re: zfcp and SLES 9 64-bit
Matt Gourley wrote: I've run into an interesting issue with SLES 9 64-bit and zfcp and was hoping someone here had an idea to fix it. I've checked the archives but saw nothing matching this. I've got a 50G FCP LUN on device F100 attached to a VM named LINUX2. If I IPL SLES on LINUX2, zfcp discovers 0xF100 after /etc/init.d runs through all its startup scripts. I then need to log in as root to manually mount /dev/sda1 to my mountpoint, which happens with no trouble. Since this is a test environment, this is not a big deal, but when we move into production, this kind of intervention is less than optimal. (Call me crazy, but I'd like to avoid the 3am phone call to mount a filesystem that should be mounted on boot. :) ) Any ideas? You might try a mkinitrd to refresh the /boot/initrd file. I had an issue a few weeks back that DASD was added to an image but not recognized until late in the bootup process. Running: cd /boot mkinitrd -k vmlinux-2.6.5-7.244-s390x.gz -i initrd-2.6.5-7.244-s390x zipl may fix the issue. Make sure the DASD that you are expecting is accurately identifed. Also note that your version may differ from mine. David -- 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. If the reader of this message is not the intended recipient, you are hereby notified that your access is unauthorized, and any review, dissemination, distribution or copying of this message including any attachments is strictly prohibited. If you are not the intended recipient, please contact the sender and delete the material from any computer. -- 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
Re: IBM AIX toolkit help
PAUL WILLIAMSON wrote: It doesn't surprise me this probably happened... #:/rpm -qf /usr/lib/libc.a file /usr/lib/libc.a is not owned by any package Oh well, I hate doing a nodeps rpm...any suggestions? I know libc was fixed to comply with some linux standards, but I can't seem to find out what libc.a is provided by... Under Suse it is provided by either: glibc-devel, or glibc-devel-32bit Hope this helps, David Schaub -- 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
