<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.3.2">
</HEAD>
<BODY>
A bit late!<BR>
<BR>
I dropped cAos, as i'm far more interested in centos,<BR>
<BR>
my new url are:<BR>
<BR>
<A HREF="http://centos.crazyfrogs.org">http://centos.crazyfrogs.org</A><BR>
<BR>
rsync://centos.crazyfrogs.org::centos<BR>
<BR>
<A HREF="ftp://centos.crazyfrogs.org/pub/CentOS">ftp://centos.crazyfrogs.org/pub/CentOS</A><BR>
<BR>
i just changed dns entries from caos to centos, so wait for a few hours for propagation<BR>
<BR>
Sorry for being late!<BR>
<BR>
<BR>
<BR>
<BR>
Le mercredi 30 mars 2005 à 21:42 +0100, Lance Davis a écrit :
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Due to the split of mirrors with cAos , it will be necessary for mirrors </FONT>
<FONT COLOR="#000000">to make some changes to the way that they mirror the CentOS tree, as </FONT>
<FONT COLOR="#000000">moving forward it will no longer be a part of the caosity tree.</FONT>
<FONT COLOR="#000000">Firstly mirrors need to decide whether they are mirroring CentOS or cAos </FONT>
<FONT COLOR="#000000">or both. They are distinct operating systems, CentOS is a rebuild of </FONT>
<FONT COLOR="#000000">Enterprise Linux , whereas cAos is an rpm based distribution in its own </FONT>
<FONT COLOR="#000000">right.</FONT>
<FONT COLOR="#000000">For more information see <A HREF="http://www.centos.org">www.centos.org</A> or caos.caosity.org</FONT>
<FONT COLOR="#000000">At present both trees are mirrored with a single rsync of </FONT>
<FONT COLOR="#000000">mirror.caosity.org::cAos - moving forward two rsyncs will be needed :-</FONT>
<FONT COLOR="#000000">mirror.caosity.org::caosity that will get the caos tree</FONT>
<FONT COLOR="#000000">and</FONT>
<FONT COLOR="#000000">msync.centos.org::CentOS that will get the CentOS tree</FONT>
<FONT COLOR="#000000">Please note that at present CentOS will be listed and stored within the </FONT>
<FONT COLOR="#000000">cAos tree, this should not be the case in the future - CentOS should never </FONT>
<FONT COLOR="#000000">be stored or listed as a part of cAos or caosity.</FONT>
<FONT COLOR="#000000">Mirror Changes</FONT>
<FONT COLOR="#000000">--------------</FONT>
<FONT COLOR="#000000">In order to achieve the changes required with minimum download bandwidth </FONT>
<FONT COLOR="#000000">the following steps should be carried out. (Note that individual </FONT>
<FONT COLOR="#000000">circumstances may vary - if in doubt do nothing and ask) .</FONT>
<FONT COLOR="#000000">1. Stop cron based rsync job from syncing</FONT>
<FONT COLOR="#000000">2. Move the CentOS tree to its new location, which should be at the root </FONT>
<FONT COLOR="#000000"> of the publically served tree. </FONT>
<FONT COLOR="#000000"> This can either be achieved with 'mv' or if you want a 2nd chance at it </FONT>
<FONT COLOR="#000000"> 'cp -al' which will create a hardlinked copy of the tree (as long as it </FONT>
<FONT COLOR="#000000"> is on the same partition)</FONT>
<FONT COLOR="#000000"> eg with directory structure /pub</FONT>
<FONT COLOR="#000000"> /pub/caos</FONT>
<FONT COLOR="#000000"> /pub/caos/centos</FONT>
<FONT COLOR="#000000"> cp -al /pub/caos/centos /pub/</FONT>
<FONT COLOR="#000000"> or</FONT>
<FONT COLOR="#000000"> mv /pub/caos/centos /pub</FONT>
<FONT COLOR="#000000"> to end up with /pub/</FONT>
<FONT COLOR="#000000"> /pub/caos</FONT>
<FONT COLOR="#000000"> /pub/centos</FONT>
<FONT COLOR="#000000"> (and /pub/caos/centos/ if using cp -al)</FONT>
<FONT COLOR="#000000">3. Create a new rsync cron job to sync the CentOS tree (if required) . </FONT>
<FONT COLOR="#000000">This should be something like :-</FONT>
<FONT COLOR="#000000"> rsync -aqzH --delete msync.centos.org::CentOS /pub/</FONT>
<FONT COLOR="#000000"> *** note the change to msync.centos.org *** mirror.centos.org is </FONT>
<FONT COLOR="#000000"> deprecated for rsync use - to allow us to use different servers for yum </FONT>
<FONT COLOR="#000000"> mirrors.</FONT>
<FONT COLOR="#000000"> please use rsync -anvzH --delete msync.centos.org::CentOS /pub/ </FONT>
<FONT COLOR="#000000"> first to test that the command will do the right thing ('n' is dry run </FONT>
<FONT COLOR="#000000"> and will just show what wil be transferred - which in theory should be very </FONT>
<FONT COLOR="#000000"> little - if it says 40 GB + then the command is wrong !!)</FONT>
<FONT COLOR="#000000">Note that due to the way that rsync works any updates will only be written </FONT>
<FONT COLOR="#000000">to this new tree and not the hardlinked tree left behind if using cp -al </FONT>
<FONT COLOR="#000000">above ( that can be deleted once you are happy with the new location </FONT>
<FONT COLOR="#000000">working).</FONT>
<FONT COLOR="#000000">4. Create a new rsync cron job to sync the cAos tree (if required). This </FONT>
<FONT COLOR="#000000">should be something like :-</FONT>
<FONT COLOR="#000000"> rsync -aqzH --delete mirror.caosity.org::caosity /pub/</FONT>
<FONT COLOR="#000000"> *** note the change to ::caosity - ::cAos will still sync both trees </FONT>
<FONT COLOR="#000000"> for mirrors that havent restructured yet. ***</FONT>
<FONT COLOR="#000000"> This will also delete the CentOS tree left underneath the caos tree </FONT>
<FONT COLOR="#000000"> above.</FONT>
<FONT COLOR="#000000">You should now have both trees in the correct places.</FONT>
<FONT COLOR="#000000">5. Please email the list to say that you have restructured your mirror and </FONT>
<FONT COLOR="#000000">what the new urls will be for public use. We will update the databases to </FONT>
<FONT COLOR="#000000">reflect these new locations.</FONT>
<FONT COLOR="#000000">6. It is not necessary to mirror all of centos if you do not wish to - eg </FONT>
<FONT COLOR="#000000">you can choose whether to carry 2.1 , 3.3, 3.4, 4.0 - but please note in </FONT>
<FONT COLOR="#000000">the email any trees that you will not be carrying and we will note that in </FONT>
<FONT COLOR="#000000">the database.</FONT>
<FONT COLOR="#000000">7. In the very near future we will be restricting access to </FONT>
<FONT COLOR="#000000">msync.centos.org to publically listed mirrors only - we have to establiush </FONT>
<FONT COLOR="#000000">a way for new mirrors to sync first though.</FONT>
<FONT COLOR="#000000">8. We will be tracking which mirrors have/havent restructured and will </FONT>
<FONT COLOR="#000000">contact individual mirrors accordingly.</FONT>
<FONT COLOR="#000000"> There is now an irc channel - #centos-mirror </FONT>
<FONT COLOR="#000000">on irc.freenode.net where mirroring discussions may be held.</FONT>
<FONT COLOR="#000000">Lance</FONT>
<FONT COLOR="#000000">-- </FONT>
<FONT COLOR="#000000">uklinux.net - </FONT>
<FONT COLOR="#000000">The ISP of choice for the discerning Linux user. </FONT>
<FONT COLOR="#000000">_______________________________________________</FONT>
<FONT COLOR="#000000">CentOS-mirror mailing list</FONT>
<FONT COLOR="#000000"><A HREF="mailto:CentOS-mirror@centos.org">CentOS-mirror@centos.org</A></FONT>
<FONT COLOR="#000000"><A HREF="http://lists.centos.org/mailman/listinfo/centos-mirror">http://lists.centos.org/mailman/listinfo/centos-mirror</A></FONT>
</PRE>
</BLOCKQUOTE>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
--<BR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD VALIGN="top">
<B>Panorapix </B><BR>
<B>Paladin level 32</B><BR>
<B>Dalaran</B>
</TD>
<TD>
<DIV ALIGN=right><IMG SRC="cid:1113991286.7654.101.camel@Ruatha.neotion.int" ALIGN="bottom" BORDER="0"></DIV><BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</TD>
</TR>
</TABLE>
</TD>
</TR>
</TABLE>
</BODY>
</HTML>