64-bit kolab?

[Bernhard Reiter]

Am Mittwoch, 20. Januar 2010 15:31:22 schrieb Gavin McCullagh:
> 1. Keep maintenance as simple as possible (I may not always be the
>    maintainer).  Security patches involving download, compile and install
>    is not the simplest route.
> 2. Keep as closely as possible to the kolab user norms so that if I or
>    someone else ask the mailing list for help down the road, the problems
>    I'm seeing are most likely something someone else has seen.

The Kolab Server recommended way is to use OpenPKG packages source compiled.
The 32bit binary packages are a very specific convenience solution (and might 
not even work best on different 32bit machines).

Security patching in source usually is quite simple. If you fear larger 
interruptions you would use your staging system (for all major IT systems it 
is good to have a staging system.) and then use the resulting personal 
binaries.

> If there's a real advantage to running 64-bit, I can do it but if not, I'm 
> inclined to stick to the packages.  I'm guessing individual kolab processes
> shouldn't need very large memory and there's unlikely to be much need for
> very high precision floating point calculations.  There might be some other
> benefit though.

As far as I remember the 64 advantages are minimal in the regular case.
Bernhard



-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/users/attachments/20100121/a52a75a9/attachment.sig>