Kristian Kielhofner wrote:
> Darrick Hartman wrote:
>   
>> I just confirmed that this does not work. uclibc does not use zoneinfo. 
>> It uses /etc/TZ. Here's how I tested.
>>
>> I copied the /usr/share/zoneinfo/US/Central from CentOS to my build 
>> environment. I then entered the build environment as a chroot (chroot 
>> build_i586/root/ ). I copied /usr/share/zoneinfo/US/Central to 
>> /tmp/etc/localtime.
>>
>> The date command still showed UTC. So I copied that file to /tmp/etc/TZ. 
>> date still showed UTC. Deleted /tmp/etc/TZ, then created a new file with 
>> only the following line: CST5CDT. date then showed the correct value.
>>
>> Bottom line is we do need both /etc/localtime and /etc/TZ and their 
>> values are not the same. Therefore, we do need two variables.
>>
>> Darrick
>>     
>
>       What I am saying is that Asterisk should be the ONLY application that 
> uses /usr/share/zoneinfo.  The rest of the system should still get it's 
> time using uclibc.  After all, that is the C library of the system. 
> Applications that can read the zoneinfo files and choose to set their 
> dates according to them (like Asterisk) can look in /usr/share/zoneinfo 
> like they always have.  Asterisk obviously does not use the system TZ 
> setting for voicemail.
>
>       Why do we need two variables?
>
>   
We don't.  I was misunderstanding something earlier.  My follow up email 
should explain what I was thinking.

Additionally, the zoneinfo files should only add a few MB, not the 11MB 
that I originally though.  It seems there are several variations in the 
CentOS install. 

CentOS has /usr/share/zoneinfo/
posix  3.4M
right 3.4M
SystemV 112K

Removing those directories leaves 2.3M which is tolerable.

Darrick

-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com
_______________________________________________
Astlinux-users mailing list
[email protected]
http://lists.kriscompanies.com/mailman/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to [EMAIL 
PROTECTED]

Reply via email to