Re: Add LDAP support to PHP
I found that I had a nss_ldap package installed from something I was trying to do earlier. I uninstalled it, reinstalled the openldap client, and then rebuilt the php package, and php ldap support started working. I guess there was a conflict between the two packages? I'm just excited that I got it working. Now I am able to password protect my php pages with MVS ldap server authentication, which is tied to RACF. Pretty Cool! Thanks for you help, Russell Jones ANPAC -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Friday, October 24, 2008 5:13 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Add LDAP support to PHP On 10/13/2008 at 4:30 PM, in message [EMAIL PROTECTED] , Jones, Russell [EMAIL PROTECTED] wrote: I am back to getting this error at apache startup: PHP Warning: Unknown(): Unable to load dynamic library '/usr/lib/php/extensions/php_ldap.so' - /usr/lib/php/extensions/php_ldap.so: cannot open shared object file: No such file or directory in Unknown on line 0 The php build does not seem to be creating the php_ldap.so module. I am not sure where to get it or how to create it. I am using the --with-ldap=shared,/usr parameter on the php_configure(). This is happening because you had a problem when you installed the openldap-client package, and then removed it. You can't build LPAP support into PHP unless you have the openldap-client package installed first. If you really, really want to do this, you'll need to work on figuring out what is going wrong with openlpap-client installed so it can be fixed. Mark Post -- 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
Re: Crytographic processors
I have followed your discussion and I think there are some misunderstandings. First let me give you a short outline of crypto on IBM System z. There is CPACF (CP Assist for Cryptographic Function), which is a function unit within the CPs. CPACF supports a couple of symmetric crypto operations like DES, AES, ..., as well as PRNG and SHA algorithms. If you have the feature code for CPACF enabled, which is a non-charge feature, you can use hardware acceleration for these operations. Exploitation of the CPACF instructions is provided by a user space library called libica. Then there are also cryptographic coprocessors available for System z. The cryptographic coprocessors support acceleration of the RSA algorithm. Access to the coprocessors is provided by the cryptographic device driver zcrypt (a.k.a. z90crypt). Exploitation for applications is provided by libica. Libica and the cryptographic device driver are open source. Further documentation can be found in Chapter 6 of Device Drivers, Features and Commands http://download.boulder.ibm.com/ibmdl/pub/software/dw/linux390/docu/l26ddd00.pdf Kevin, you are asking for performance figures. Maybe this link on IBM developerworks can help: http://www.ibm.com/developerworks/linux/linux390/perf/tuning_res_security_crypto.html Regards, Felix John Summerfield wrote: Kevin Evans wrote: Has anbody had the Z9 cryptographic processors turned on for IFL use? If so, do you have any performance figures? Many thanks, shrug These emails are fine. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- 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
Re: Zfcp.conf
Duh, no. I'll try it. Is this a guess or have you been successful? Thanks, Betsie -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Romanowski, John (OFT) Sent: Friday, October 24, 2008 7:38 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Zfcp.conf Betsie, After changing zfcp.conf did you run mkinitrd and zipl before rebooting? This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Spann, Elizebeth (Betsie) Sent: Friday, October 24, 2008 7:29 PM To: LINUX-390@VM.MARIST.EDU Subject: Zfcp.conf Hi, I changed my zfcp.conf file and rebooted.I did not erase the multipath_bindings file. RHEL 5. device-mapper-multipath-0.4.7-17.el5 My multipath.conf is configured to use multipath_bindings file I left the LUNs in the same order but changed zfcp.conf fields 1 and 3; i.e. the FCP device and the WWPN. After the reboot, the original paths were still being used. I checked this with multipath -ll and lsscsi. All the hosts are listed with lszfcp but not all are in multipath -ll. Can the LUN order in zfcp.conf be changed if I retain the same multipath_bindings file? I don't understand how the two files are related. I thought the multipath_bindings file preserved the mpathxx assignment to the devices. I thought the zfcp.conf file assigned LUNs to FCP routes. Betsie -- 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
Re: Zfcp.conf
I don't actually have any Redhats myself but an IBM manual said after changing Redhat's zfcp.conf it's necessary to re-run mkinitrd and zipl to make the zfcp.conf changes survive (take effect) at reboot. Given that and you said After the reboot, the original paths were still being used., I suspect the initrd's got the prior contents of zipl.conf built into it and doesn't know yet about your changes to the zfcp.conf file. This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Spann, Elizebeth (Betsie) Sent: Monday, October 27, 2008 11:21 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Zfcp.conf Duh, no. I'll try it. Is this a guess or have you been successful? Thanks, Betsie -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Romanowski, John (OFT) Sent: Friday, October 24, 2008 7:38 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Zfcp.conf Betsie, After changing zfcp.conf did you run mkinitrd and zipl before rebooting? This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Spann, Elizebeth (Betsie) Sent: Friday, October 24, 2008 7:29 PM To: LINUX-390@VM.MARIST.EDU Subject: Zfcp.conf Hi, I changed my zfcp.conf file and rebooted.I did not erase the multipath_bindings file. RHEL 5. device-mapper-multipath-0.4.7-17.el5 My multipath.conf is configured to use multipath_bindings file I left the LUNs in the same order but changed zfcp.conf fields 1 and 3; i.e. the FCP device and the WWPN. After the reboot, the original paths were still being used. I checked this with multipath -ll and lsscsi. All the hosts are listed with lszfcp but not all are in multipath -ll. Can the LUN order in zfcp.conf be changed if I retain the same multipath_bindings file? I don't understand how the two files are related. I thought the multipath_bindings file preserved the mpathxx assignment to the devices. I thought the zfcp.conf file assigned LUNs to FCP routes. Betsie -- 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 -- 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.conf
my earlier response said I suspect the initrd's got the prior contents of zipl.conf built into it I meant meant zfcp.conf too many z...conf's in my life or i need more zz's This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Spann, Elizebeth (Betsie) Sent: Monday, October 27, 2008 11:21 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Zfcp.conf Duh, no. I'll try it. Is this a guess or have you been successful? Thanks, Betsie -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Romanowski, John (OFT) Sent: Friday, October 24, 2008 7:38 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Zfcp.conf Betsie, After changing zfcp.conf did you run mkinitrd and zipl before rebooting? This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Spann, Elizebeth (Betsie) Sent: Friday, October 24, 2008 7:29 PM To: LINUX-390@VM.MARIST.EDU Subject: Zfcp.conf Hi, I changed my zfcp.conf file and rebooted.I did not erase the multipath_bindings file. RHEL 5. device-mapper-multipath-0.4.7-17.el5 My multipath.conf is configured to use multipath_bindings file I left the LUNs in the same order but changed zfcp.conf fields 1 and 3; i.e. the FCP device and the WWPN. After the reboot, the original paths were still being used. I checked this with multipath -ll and lsscsi. All the hosts are listed with lszfcp but not all are in multipath -ll. Can the LUN order in zfcp.conf be changed if I retain the same multipath_bindings file? I don't understand how the two files are related. I thought the multipath_bindings file preserved the mpathxx assignment to the devices. I thought the zfcp.conf file assigned LUNs to FCP routes. Betsie -- 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 -- 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.conf
No, it's not necessary, if everything has been done properly. It has to do with when in the boot process the FCP devices are attached. If you ALLOW mkinitrd to put zfcp.conf in the initrd, those disks will be attached before the root filesystem is mounted. If you're okay with that, then it's fine. But if you want more flexibility, it might make more sense to remove zfcp.conf entirely before running mkinitrd. That way, NO FCP disks are attached before the root filesystem mounts, so it's all handled later in the boot process, and it all still works. There are a couple of gotchas with this. In versions prior to RHEL5.2, zfcpconf.sh was run out of /etc/rc.s/rc.sysinit. This resulted in a chicken-egg situation when multipath and/or LVM were used, and Red Hat went through several iterations trying to fix it, going all the way back to RHEL4.4. 5.2 triggers the script out of udev, which also nicely solves a race condition in rc.sysinit, where udev doesn't build the device nodes fast enough for LVM to catch them. Far as multipath goes, I don't see why changing the WWPN and Bus ID should have changed the identifier that's stored in the bindings file, but it's possible, since I forget how that's calculated. The simplest way to straighten it all out is to run multipath -F, remove all entries from the bindings file, and then run multipath, and let them rebuild. You might have to check to be sure you're mounting filesystems on the right places, though, if you're mounting by node. We're planning to standardize on either using LVM, or mount by label, to avoid this. Two other quick hints: The default location for the bindings file is in /var/lib. If /var is on a separate filesystem from root, the bindings file will be built in the wrong place, or not built at all, and /var will be mounted over it. The latest versions of device-mapper-multipath have a parameter in /etc/multipath.conf that allows you to specify the location of the bindings file. Earlier versions required it to be changed via command line parm, which, of course, required you do surgery on the init script. Finally, the version of mount that comes with RHEL5.2 uses a new scheme to prioritize mounts so that multipath devices and their components don't look like the same disk. This used to cause mount-by-label to fail. If you start getting mount failures, device busy, or duplicate device messages, check file /etc/blkid/blkid.tab. If you've added and removed LUNs, this file can contain residual data that confuses mount. Just delete it, and reboot, it will be rebuilt properly. Good luck! -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Romanowski, John (OFT) Sent: Monday, October 27, 2008 11:31 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Zfcp.conf I don't actually have any Redhats myself but an IBM manual said after changing Redhat's zfcp.conf it's necessary to re-run mkinitrd and zipl to make the zfcp.conf changes survive (take effect) at reboot. Given that and you said After the reboot, the original paths were still being used., I suspect the initrd's got the prior contents of zipl.conf built into it and doesn't know yet about your changes to the zfcp.conf file. This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Spann, Elizebeth (Betsie) Sent: Monday, October 27, 2008 11:21 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Zfcp.conf Duh, no. I'll try it. Is this a guess or have you been successful? Thanks, Betsie -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Romanowski, John (OFT) Sent: Friday, October 24, 2008 7:38 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Zfcp.conf Betsie, After changing zfcp.conf did you run mkinitrd and zipl before rebooting? This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Spann, Elizebeth (Betsie) Sent: Friday, October 24, 2008 7:29 PM To: LINUX-390@VM.MARIST.EDU
Daylight Savings Time adjustment
Over the weekend, my Slack/390 system fell back an hour for daylight savings time. How do I adjust when this happens? I think it's supposed to happen next week. Russell Jones ANPAC -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Hall, Ken (GTS) Sent: Monday, October 27, 2008 11:23 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Zfcp.conf No, it's not necessary, if everything has been done properly. It has to do with when in the boot process the FCP devices are attached. If you ALLOW mkinitrd to put zfcp.conf in the initrd, those disks will be attached before the root filesystem is mounted. If you're okay with that, then it's fine. But if you want more flexibility, it might make more sense to remove zfcp.conf entirely before running mkinitrd. That way, NO FCP disks are attached before the root filesystem mounts, so it's all handled later in the boot process, and it all still works. There are a couple of gotchas with this. In versions prior to RHEL5.2, zfcpconf.sh was run out of /etc/rc.s/rc.sysinit. This resulted in a chicken-egg situation when multipath and/or LVM were used, and Red Hat went through several iterations trying to fix it, going all the way back to RHEL4.4. 5.2 triggers the script out of udev, which also nicely solves a race condition in rc.sysinit, where udev doesn't build the device nodes fast enough for LVM to catch them. Far as multipath goes, I don't see why changing the WWPN and Bus ID should have changed the identifier that's stored in the bindings file, but it's possible, since I forget how that's calculated. The simplest way to straighten it all out is to run multipath -F, remove all entries from the bindings file, and then run multipath, and let them rebuild. You might have to check to be sure you're mounting filesystems on the right places, though, if you're mounting by node. We're planning to standardize on either using LVM, or mount by label, to avoid this. Two other quick hints: The default location for the bindings file is in /var/lib. If /var is on a separate filesystem from root, the bindings file will be built in the wrong place, or not built at all, and /var will be mounted over it. The latest versions of device-mapper-multipath have a parameter in /etc/multipath.conf that allows you to specify the location of the bindings file. Earlier versions required it to be changed via command line parm, which, of course, required you do surgery on the init script. Finally, the version of mount that comes with RHEL5.2 uses a new scheme to prioritize mounts so that multipath devices and their components don't look like the same disk. This used to cause mount-by-label to fail. If you start getting mount failures, device busy, or duplicate device messages, check file /etc/blkid/blkid.tab. If you've added and removed LUNs, this file can contain residual data that confuses mount. Just delete it, and reboot, it will be rebuilt properly. Good luck! -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Romanowski, John (OFT) Sent: Monday, October 27, 2008 11:31 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Zfcp.conf I don't actually have any Redhats myself but an IBM manual said after changing Redhat's zfcp.conf it's necessary to re-run mkinitrd and zipl to make the zfcp.conf changes survive (take effect) at reboot. Given that and you said After the reboot, the original paths were still being used., I suspect the initrd's got the prior contents of zipl.conf built into it and doesn't know yet about your changes to the zfcp.conf file. This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Spann, Elizebeth (Betsie) Sent: Monday, October 27, 2008 11:21 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Zfcp.conf Duh, no. I'll try it. Is this a guess or have you been successful? Thanks, Betsie -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Romanowski, John (OFT) Sent: Friday, October 24, 2008 7:38 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Zfcp.conf Betsie, After changing zfcp.conf did you run mkinitrd and zipl before rebooting? This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it
Re: Daylight Savings Time adjustment
On Monday 27 October 2008 13:08, Jones, Russell wrote: Over the weekend, my Slack/390 system fell back an hour for daylight savings time. How do I adjust when this happens? I think it's supposed to happen next week. You have to get the current set of compiled timezone files into /usr/share/zoneinfo. That should be available for Slackware by now. If not, you can get the sources for the zoneinfo files here: ftp://elsie.nci.nih.gov/pub. - MacK. - Edmund R. MacKenty Software Architect Rocket Software, Inc. Newton, MA USA -- 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: Daylight Savings Time adjustment
Have you got the latest 'tzdata' package? You may want to get that and install it .. (I'm assuming Slackware uses it ... not familiar with Slack) Scott Rohling On Mon, Oct 27, 2008 at 11:08 AM, Jones, Russell [EMAIL PROTECTED]wrote: Over the weekend, my Slack/390 system fell back an hour for daylight savings time. How do I adjust when this happens? I think it's supposed to happen next week. Russell Jones ANPAC -- 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: Daylight Savings Time adjustment
Found it. I had to upgrade my glibc-zoneinfo package. I couldn't find any source code for the package, but apparently it is not architecture dependent. I installed glibc-zoneinfo-2.7-noarch-10.tgz, and my time was corrected. We'll see what happens when daylight savings changes. Thanks Russell Jones ANPAC -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Scott Rohling Sent: Monday, October 27, 2008 12:20 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Daylight Savings Time adjustment Have you got the latest 'tzdata' package? You may want to get that and install it .. (I'm assuming Slackware uses it ... not familiar with Slack) Scott Rohling On Mon, Oct 27, 2008 at 11:08 AM, Jones, Russell [EMAIL PROTECTED]wrote: Over the weekend, my Slack/390 system fell back an hour for daylight savings time. How do I adjust when this happens? I think it's supposed to happen next week. Russell Jones ANPAC -- 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
Re: Daylight Savings Time adjustment
Jones, Russell wrote: Found it. I had to upgrade my glibc-zoneinfo package. I couldn't find any source code for the package, but apparently it is not architecture dependent. Some time ago, when our now-expelled govt thought to introduce daylight saving on short notice, various software suppliers found the notice too short. I found the timezone data from one Linux distro on Intellish worked not only on others, but also on OSX on PowerPC. I only copied /etc/localtime -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- 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
