ipcop-devel Mailing List for IPCop Firewall

Thanks Achim
That's fixed it here too.

Eric


On 18 November 2013 12:47, Achim Weber <dot...@gm...> wrote:

> I did a fresh 2.0.6 installation (install 2.0.3 + update to 2.0.6). Copy
> update-2.1.0 and update-2.1.1 (SVN rev 7132) und installed those updates.
> No
> problems.
>
> With the (wrong) gawk update (SVN rev 7130?) I had same error as you Eric.
>
> Achim
>
>
>
> > Hi!
> >
> > This may also a problem of my gawk update. I reverted the update and
> building
> > now. Will check and report back...
> >
> > Achim
> >
> >
> >
> >> Oops, wrong list. Thanks for pointing that out David.
> >> Eric
> >>
> >>
> >> On 17 November 2013 17:33, David W Studeman <da...@da...>
> wrote:
> >>
> >>> On 11/17/2013 9:08 AM, Eric Oberlander wrote:
> >>>> Hi chaps
> >>>>
> >>>> I'm getting this error when I apply the 2.1.1 update to my IPCop v2.1
> >>>> testbox:
> >>>>
> >>>> Boot configfile already has 3.4-1.
> >>>> Copying many modules.  This may take some time .... Done
> >>>> Copying firmware ... Done
> >>>> Creating ipcoprd.img.  This may take some time ... Done
> >>>> awk: error while loading shared libraries: libmpfr.so.1: cannot open
> >>> shared
> >>>> object file:  No such file or directory
> >>>> ERROR: Not enough space on /boot.
> >>>> 2.1.1 update installed.
> >>>>
> >>>> Eric
> >>>
> >>> Did you mean this to be on the devel list?
> >>>
> >>> I was always wondering where the mechanism is that should be relinking
> >>> to the new kernel. I hadn't looked in updatekernel.pl in a while so I
> >>> cannot comment whether it is in that file. You really need to lose the
> >>> 3.0 kernel stuff as it will never be in any production version. How do
> >>> these updates fare when updating a 2.0.6 box? Yes, we fake out an
> >>> existing 2.1.1svn trunk build to test updates but it only counts if
> >>> 2.0.6 can be updated cleanly.
> >>>
> >>> On my Raqcop updates I actually include the symlinks to the kernel
> image
> >>> AND map in the update tarball. Since there is no bootloader on a
> Cobalt,
> >>> there is no reason to keep any old images since without symplinks they
> >>> will never boot so my updatekernel.pl is modified to remove the last
> one
> >>> and keep only the new one. On a Cobalt, the rom looks for vmlinux.gz or
> >>> vmlinux.bz2 only so I have to have said symlinks to the kernel image
> >>> which is named after the kernel version or it will never boot.
> >>>
> >>> Another thought would be to put fake 2.6.32 kernel image and
> >>> /lib/modules, move the 3.x stuff out of the way and see what happens.
> On
> >>> a standard IPCop, updatekernel.pl deletes old images except for the
> last
> >>> one so it would keep 2.6.32, add 3.4.x and go from there.
> >>>
> >>> --
> >>> Dave Studeman
> >>> http://www.raqcop.com
> >>>
> >>>
> >>>
> >>>
> ------------------------------------------------------------------------------
> >>> DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
> >>> OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
> >>> Free app hosting. Or install the open source package on any LAMP
> server.
> >>> Sign up and see examples for AngularJS, jQuery, Sencha Touch and
> Native!
> >>>
> http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
> >>> _______________________________________________
> >>> IPCop-user mailing list
> >>> IPC...@li...
> >>> https://lists.sourceforge.net/lists/listinfo/ipcop-user
> >>>
> >>
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
> >> OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
> >> Free app hosting. Or install the open source package on any LAMP server.
> >> Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
> >>
> http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
> >>
> >>
> >>
> >> _______________________________________________
> >> IPCop-devel mailing list
> >> IPC...@li...
> >> https://lists.sourceforge.net/lists/listinfo/ipcop-devel
> >>
> >
> >
> >
> ------------------------------------------------------------------------------
> > DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
> > OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
> > Free app hosting. Or install the open source package on any LAMP server.
> > Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
> > _______________________________________________
> > IPCop-devel mailing list
> > IPC...@li...
> > https://lists.sourceforge.net/lists/listinfo/ipcop-devel
> >
>
>

I did a fresh 2.0.6 installation (install 2.0.3 + update to 2.0.6). Copy
update-2.1.0 and update-2.1.1 (SVN rev 7132) und installed those updates. No
problems.

With the (wrong) gawk update (SVN rev 7130?) I had same error as you Eric.

Achim



> Hi!
> 
> This may also a problem of my gawk update. I reverted the update and building
> now. Will check and report back...
> 
> Achim
> 
> 
> 
>> Oops, wrong list. Thanks for pointing that out David.
>> Eric
>>
>>
>> On 17 November 2013 17:33, David W Studeman <da...@da...> wrote:
>>
>>> On 11/17/2013 9:08 AM, Eric Oberlander wrote:
>>>> Hi chaps
>>>>
>>>> I'm getting this error when I apply the 2.1.1 update to my IPCop v2.1
>>>> testbox:
>>>>
>>>> Boot configfile already has 3.4-1.
>>>> Copying many modules.  This may take some time .... Done
>>>> Copying firmware ... Done
>>>> Creating ipcoprd.img.  This may take some time ... Done
>>>> awk: error while loading shared libraries: libmpfr.so.1: cannot open
>>> shared
>>>> object file:  No such file or directory
>>>> ERROR: Not enough space on /boot.
>>>> 2.1.1 update installed.
>>>>
>>>> Eric
>>>
>>> Did you mean this to be on the devel list?
>>>
>>> I was always wondering where the mechanism is that should be relinking
>>> to the new kernel. I hadn't looked in updatekernel.pl in a while so I
>>> cannot comment whether it is in that file. You really need to lose the
>>> 3.0 kernel stuff as it will never be in any production version. How do
>>> these updates fare when updating a 2.0.6 box? Yes, we fake out an
>>> existing 2.1.1svn trunk build to test updates but it only counts if
>>> 2.0.6 can be updated cleanly.
>>>
>>> On my Raqcop updates I actually include the symlinks to the kernel image
>>> AND map in the update tarball. Since there is no bootloader on a Cobalt,
>>> there is no reason to keep any old images since without symplinks they
>>> will never boot so my updatekernel.pl is modified to remove the last one
>>> and keep only the new one. On a Cobalt, the rom looks for vmlinux.gz or
>>> vmlinux.bz2 only so I have to have said symlinks to the kernel image
>>> which is named after the kernel version or it will never boot.
>>>
>>> Another thought would be to put fake 2.6.32 kernel image and
>>> /lib/modules, move the 3.x stuff out of the way and see what happens. On
>>> a standard IPCop, updatekernel.pl deletes old images except for the last
>>> one so it would keep 2.6.32, add 3.4.x and go from there.
>>>
>>> --
>>> Dave Studeman
>>> http://www.raqcop.com
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
>>> OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
>>> Free app hosting. Or install the open source package on any LAMP server.
>>> Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
>>> http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> IPCop-user mailing list
>>> IPC...@li...
>>> https://lists.sourceforge.net/lists/listinfo/ipcop-user
>>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
>> OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
>> Free app hosting. Or install the open source package on any LAMP server.
>> Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
>> http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
>>
>>
>>
>> _______________________________________________
>> IPCop-devel mailing list
>> IPC...@li...
>> https://lists.sourceforge.net/lists/listinfo/ipcop-devel
>>
> 
> 
> ------------------------------------------------------------------------------
> DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
> OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
> Free app hosting. Or install the open source package on any LAMP server.
> Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
> http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
> _______________________________________________
> IPCop-devel mailing list
> IPC...@li...
> https://lists.sourceforge.net/lists/listinfo/ipcop-devel
> 

Hi!

This may also a problem of my gawk update. I reverted the update and building
now. Will check and report back...

Achim



> Oops, wrong list. Thanks for pointing that out David.
> Eric
> 
> 
> On 17 November 2013 17:33, David W Studeman <da...@da...> wrote:
> 
>> On 11/17/2013 9:08 AM, Eric Oberlander wrote:
>>> Hi chaps
>>>
>>> I'm getting this error when I apply the 2.1.1 update to my IPCop v2.1
>>> testbox:
>>>
>>> Boot configfile already has 3.4-1.
>>> Copying many modules.  This may take some time .... Done
>>> Copying firmware ... Done
>>> Creating ipcoprd.img.  This may take some time ... Done
>>> awk: error while loading shared libraries: libmpfr.so.1: cannot open
>> shared
>>> object file:  No such file or directory
>>> ERROR: Not enough space on /boot.
>>> 2.1.1 update installed.
>>>
>>> Eric
>>
>> Did you mean this to be on the devel list?
>>
>> I was always wondering where the mechanism is that should be relinking
>> to the new kernel. I hadn't looked in updatekernel.pl in a while so I
>> cannot comment whether it is in that file. You really need to lose the
>> 3.0 kernel stuff as it will never be in any production version. How do
>> these updates fare when updating a 2.0.6 box? Yes, we fake out an
>> existing 2.1.1svn trunk build to test updates but it only counts if
>> 2.0.6 can be updated cleanly.
>>
>> On my Raqcop updates I actually include the symlinks to the kernel image
>> AND map in the update tarball. Since there is no bootloader on a Cobalt,
>> there is no reason to keep any old images since without symplinks they
>> will never boot so my updatekernel.pl is modified to remove the last one
>> and keep only the new one. On a Cobalt, the rom looks for vmlinux.gz or
>> vmlinux.bz2 only so I have to have said symlinks to the kernel image
>> which is named after the kernel version or it will never boot.
>>
>> Another thought would be to put fake 2.6.32 kernel image and
>> /lib/modules, move the 3.x stuff out of the way and see what happens. On
>> a standard IPCop, updatekernel.pl deletes old images except for the last
>> one so it would keep 2.6.32, add 3.4.x and go from there.
>>
>> --
>> Dave Studeman
>> http://www.raqcop.com
>>
>>
>>
>> ------------------------------------------------------------------------------
>> DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
>> OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
>> Free app hosting. Or install the open source package on any LAMP server.
>> Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
>> http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
>> _______________________________________________
>> IPCop-user mailing list
>> IPC...@li...
>> https://lists.sourceforge.net/lists/listinfo/ipcop-user
>>
> 
> 
> 
> ------------------------------------------------------------------------------
> DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
> OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
> Free app hosting. Or install the open source package on any LAMP server.
> Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
> http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
> 
> 
> 
> _______________________________________________
> IPCop-devel mailing list
> IPC...@li...
> https://lists.sourceforge.net/lists/listinfo/ipcop-devel
> 

Hi Dave,

>   It seems as though gawk wants mpfr libraries available now whereas I
> don't think it did before. I see this:
> 
> /usr/bin/awk: error while loading shared libraries: libmpfr.so.1: cannot 
> open shared object file: No such file or directory

yes, this was my mistake. I didn't notice gawk is in the toolchain. I reverted
gawk to 4.0.2.

Achim

  It seems as though gawk wants mpfr libraries available now whereas I 
don't think it did before. I see this:

/usr/bin/awk: error while loading shared libraries: libmpfr.so.1: cannot 
open shared object file: No such file or directory

I was installing a slightly hacked (to run on the newer kernel) version 
of wlanap when I got the above error although wlanap did start and I 
could see it from wifi capable devices. I pulled over the missing 
library from my build tree (according to gawk) and reinstalled the 
wlanap with no error.
-- 
Dave Studeman
http://www.raqcop.com

Oops, wrong list. Thanks for pointing that out David.
Eric


On 17 November 2013 17:33, David W Studeman <da...@da...> wrote:

> On 11/17/2013 9:08 AM, Eric Oberlander wrote:
> > Hi chaps
> >
> > I'm getting this error when I apply the 2.1.1 update to my IPCop v2.1
> > testbox:
> >
> > Boot configfile already has 3.4-1.
> > Copying many modules.  This may take some time .... Done
> > Copying firmware ... Done
> > Creating ipcoprd.img.  This may take some time ... Done
> > awk: error while loading shared libraries: libmpfr.so.1: cannot open
> shared
> > object file:  No such file or directory
> > ERROR: Not enough space on /boot.
> > 2.1.1 update installed.
> >
> > Eric
>
> Did you mean this to be on the devel list?
>
> I was always wondering where the mechanism is that should be relinking
> to the new kernel. I hadn't looked in updatekernel.pl in a while so I
> cannot comment whether it is in that file. You really need to lose the
> 3.0 kernel stuff as it will never be in any production version. How do
> these updates fare when updating a 2.0.6 box? Yes, we fake out an
> existing 2.1.1svn trunk build to test updates but it only counts if
> 2.0.6 can be updated cleanly.
>
> On my Raqcop updates I actually include the symlinks to the kernel image
> AND map in the update tarball. Since there is no bootloader on a Cobalt,
> there is no reason to keep any old images since without symplinks they
> will never boot so my updatekernel.pl is modified to remove the last one
> and keep only the new one. On a Cobalt, the rom looks for vmlinux.gz or
> vmlinux.bz2 only so I have to have said symlinks to the kernel image
> which is named after the kernel version or it will never boot.
>
> Another thought would be to put fake 2.6.32 kernel image and
> /lib/modules, move the 3.x stuff out of the way and see what happens. On
> a standard IPCop, updatekernel.pl deletes old images except for the last
> one so it would keep 2.6.32, add 3.4.x and go from there.
>
> --
> Dave Studeman
> http://www.raqcop.com
>
>
>
> ------------------------------------------------------------------------------
> DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
> OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
> Free app hosting. Or install the open source package on any LAMP server.
> Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
> http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
> _______________________________________________
> IPCop-user mailing list
> IPC...@li...
> https://lists.sourceforge.net/lists/listinfo/ipcop-user
>

On 11/09/2013 02:39 AM, Achim Weber wrote:
> Hi David
>
> thanks for the hint. The idea behind the current update rootfiles is to avoid
> packaging files which are not changed and only increase update package size.
>
> It is working again, there where some trailing spaces which confuses the update
> tar...
>
>
> Achim
>
>

Oh ok, now I understand why there were some multiple entries but not all 
of them or just one uncommented entry to capture all of them.

I've been bitten by trailing spaces in rootfiles myself and finally 
figured out how to avoid them. Nothing like removing an invisible problem.

-- 
Dave Studeman
http://www.raqcop.com

Hi David

thanks for the hint. The idea behind the current update rootfiles is to avoid
packaging files which are not changed and only increase update package size.

It is working again, there where some trailing spaces which confuses the update
tar...


Achim



> On 11/05/2013 01:24 PM, Achim Weber wrote:
> > Ups, this is not working. Have to re-check how the doc/diff-files is
> > generated/what content of diff-file means. Will look into it tomorrow.
> >
> > Achim
> >
> 
> This is the only entry you need to add for tzdata in the 2.1.1 
> rootfiles. The rest can either be commented out or ommitted. It creates 
> the 2.1.1 update fine with just this and includes every zone in there.
> 
> /usr/share/zoneinfo/
> 
> -- 
> Dave Studeman
> http://www.raqcop.com
> 
> 
> ------------------------------------------------------------------------------
> November Webinars for C, C++, Fortran Developers
> Accelerate application performance with scalable programming models. Explore
> techniques for threading, error checking, porting, and tuning. Get the most 
> from the latest Intel processors and coprocessors. See abstracts and register
> http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
> _______________________________________________
> IPCop-devel mailing list
> IPC...@li...
> https://lists.sourceforge.net/lists/listinfo/ipcop-devel

On 11/05/2013 01:24 PM, Achim Weber wrote:
> Ups, this is not working. Have to re-check how the doc/diff-files is
> generated/what content of diff-file means. Will look into it tomorrow.
>
> Achim
>

This is the only entry you need to add for tzdata in the 2.1.1 
rootfiles. The rest can either be commented out or ommitted. It creates 
the 2.1.1 update fine with just this and includes every zone in there.

/usr/share/zoneinfo/

-- 
Dave Studeman
http://www.raqcop.com

Ups, this is not working. Have to re-check how the doc/diff-files is
generated/what content of diff-file means. Will look into it tomorrow.

Achim



> Revision: 7116
>           http://sourceforge.net/p/ipcop/svn/7116
> Author:   dotzball
> Date:     2013-11-05 21:18:41 +0000 (Tue, 05 Nov 2013)
> Log Message:
> -----------
> Add updated/new tzdata-2013h files to update rootfiles.
> 
> Modified Paths:
> --------------
>     ipcop/trunk/updates/2.1.1/ROOTFILES.i486-2.1.1
> 
> Modified: ipcop/trunk/updates/2.1.1/ROOTFILES.i486-2.1.1
> ===================================================================
> --- ipcop/trunk/updates/2.1.1/ROOTFILES.i486-2.1.1	2013-11-03 15:57:52
> UTC (rev 7115) +++ ipcop/trunk/updates/2.1.1/ROOTFILES.i486-2.1.1
> 2013-11-05 21:18:41 UTC (rev 7116) @@ -33,45 +33,84 @@
>  /usr/lib/squid/errors
>  /usr/lib/squid/errors.ipcop
>  ##
> -## tzdata-2013g
> +## tzdata-2013h
>  /usr/share/zoneinfo/posix/Africa/Cairo
>  /usr/share/zoneinfo/posix/Africa/Casablanca
> +/usr/share/zoneinfo/posix/Africa/El_Aaiun               
>  /usr/share/zoneinfo/posix/Africa/Gaborone
> +/usr/share/zoneinfo/posix/Africa/Juba                   
>  /usr/share/zoneinfo/posix/Africa/Tripoli
> +/usr/share/zoneinfo/posix/America/Anguilla              
>  /usr/share/zoneinfo/posix/America/Araguaina
> +/usr/share/zoneinfo/posix/America/Argentina/San_Luis    
> +/usr/share/zoneinfo/posix/America/Aruba                 
>  /usr/share/zoneinfo/posix/America/Asuncion
> +/usr/share/zoneinfo/posix/America/Bahia
>  /usr/share/zoneinfo/posix/America/Barbados
> -/usr/share/zoneinfo/posix/America/Bahia
>  /usr/share/zoneinfo/posix/America/Bogota
> +/usr/share/zoneinfo/posix/America/Cayman                
>  /usr/share/zoneinfo/posix/America/Costa_Rica
>  /usr/share/zoneinfo/posix/America/Curacao
> +/usr/share/zoneinfo/posix/America/Dominica              
> +/usr/share/zoneinfo/posix/America/Eirunepe              
> +/usr/share/zoneinfo/posix/America/Grand_Turk            
> +/usr/share/zoneinfo/posix/America/Grenada               
> +/usr/share/zoneinfo/posix/America/Guadeloupe            
>  /usr/share/zoneinfo/posix/America/Havana
> +/usr/share/zoneinfo/posix/America/Jamaica               
>  /usr/share/zoneinfo/posix/America/Kralendijk
>  /usr/share/zoneinfo/posix/America/Lower_Princes
> +/usr/share/zoneinfo/posix/America/Marigot               
> +/usr/share/zoneinfo/posix/America/Montserrat            
>  /usr/share/zoneinfo/posix/America/Nassau
>  /usr/share/zoneinfo/posix/America/Port-au-Prince
> +/usr/share/zoneinfo/posix/America/Porto_Acre            
> +/usr/share/zoneinfo/posix/America/Rio_Branco            
>  /usr/share/zoneinfo/posix/America/Santiago
> +/usr/share/zoneinfo/posix/America/St_Barthelemy         
> +/usr/share/zoneinfo/posix/America/St_Kitts              
> +/usr/share/zoneinfo/posix/America/St_Lucia              
> +/usr/share/zoneinfo/posix/America/St_Thomas             
> +/usr/share/zoneinfo/posix/America/St_Vincent            
> +/usr/share/zoneinfo/posix/America/Tortola               
> +/usr/share/zoneinfo/posix/America/Virgin                
> +/usr/share/zoneinfo/posix/Antarctica/Macquarie          
> +/usr/share/zoneinfo/posix/Antarctica/McMurdo            
>  /usr/share/zoneinfo/posix/Antarctica/Palmer
> +/usr/share/zoneinfo/posix/Antarctica/South_Pole         
>  /usr/share/zoneinfo/posix/Asia/Aden
>  /usr/share/zoneinfo/posix/Asia/Amman
> +/usr/share/zoneinfo/posix/Asia/Dili                     
> +/usr/share/zoneinfo/posix/Asia/Gaza                     
> +/usr/share/zoneinfo/posix/Asia/Hebron                   
>  /usr/share/zoneinfo/posix/Asia/Hong_Kong
> +/usr/share/zoneinfo/posix/Asia/Jakarta                  
> +/usr/share/zoneinfo/posix/Asia/Jayapura                 
>  /usr/share/zoneinfo/posix/Asia/Jerusalem
>  /usr/share/zoneinfo/posix/Asia/Khandyga
> +/usr/share/zoneinfo/posix/Asia/Makassar                 
>  /usr/share/zoneinfo/posix/Asia/Muscat
> +/usr/share/zoneinfo/posix/Asia/Pontianak                
>  /usr/share/zoneinfo/posix/Asia/Rangoon
>  /usr/share/zoneinfo/posix/Asia/Shanghai
>  /usr/share/zoneinfo/posix/Asia/Tel_Aviv
> +/usr/share/zoneinfo/posix/Asia/Ujung_Pandang            
>  /usr/share/zoneinfo/posix/Asia/Ust-Nera
>  /usr/share/zoneinfo/posix/Atlantic/Bermuda
> +/usr/share/zoneinfo/posix/Brazil/Acre                   
>  /usr/share/zoneinfo/posix/Chile/Continental
>  /usr/share/zoneinfo/posix/Chile/EasterIsland
>  /usr/share/zoneinfo/posix/Cuba
>  /usr/share/zoneinfo/posix/Egypt
>  /usr/share/zoneinfo/posix/Europe/Busingen
> +/usr/share/zoneinfo/posix/Europe/Vaduz                  
>  /usr/share/zoneinfo/posix/Europe/Vienna
> +/usr/share/zoneinfo/posix/Europe/Zurich                 
>  /usr/share/zoneinfo/posix/Hongkong
>  /usr/share/zoneinfo/posix/Israel
> +/usr/share/zoneinfo/posix/Jamaica                       
>  /usr/share/zoneinfo/posix/Libya
> -/usr/share/zoneinfo/posix/PRC
>  /usr/share/zoneinfo/posix/Pacific/Easter
>  /usr/share/zoneinfo/posix/Pacific/Fiji
> +/usr/share/zoneinfo/posix/Pacific/Johnston              
> +/usr/share/zoneinfo/posix/PRC
> 
> This was sent by the SourceForge.net collaborative development platform, the
> world's largest Open Source development site.
> 
> 
> ------------------------------------------------------------------------------
> November Webinars for C, C++, Fortran Developers
> Accelerate application performance with scalable programming models. Explore
> techniques for threading, error checking, porting, and tuning. Get the most 
> from the latest Intel processors and coprocessors. See abstracts and register
> http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
> _______________________________________________
> Ipcop-svn mailing list
> Ipc...@li...
> https://lists.sourceforge.net/lists/listinfo/ipcop-svn