[Kolab-devel] ftp.kolab.org structure

[Bernhard Reiter]

[ Question was: How to structure ftp.kolab.org. ]

We have two solutions:
	a) put all packages in current and when a new package
	comes, move the old one in a new directory and the new one
	in current.

        Advantage: avoids for the mirror to support symlinks
        Disadvantage: move packaged get transfered to mirrors again

        b) put all packages in directories and use symlinks from current
  
        Advantage: mirrors need to get a bit less
        Disadvantage: Need mirrors to set up a document root so
        that symlinks are not followed to other parts of the server
        for security reasons


Talked to Martin on the phone,
as we have b) now and he runs the second mirror,
there is not immedeate need to change and he just can
activate symlinks on a document root or virutal server
on Erfrakon's mirror.

On Friday 03 September 2004 00:10, Martin Konold wrote:
> Am Donnerstag, 2. September 2004 10:07 schrieb Thomas Arendsen Hein:

> > Please explain your RCS approach. I know how RCS works, but I can't
> > imagine how this can be applied to a download structure with the
> > condition of never moving files around.
>
> This condition is imho less important and has to be dropped with the
> proposed RCS approach.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2145 bytes
Desc: signature
URL: <http://lists.kolab.org/pipermail/devel/attachments/20040903/6cc4f5ce/attachment.p7s>