Legacy mirror structure

Jesse Keating jkeating at j2solutions.net
Mon Jan 19 08:18:33 UTC 2004


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

My proposal is to run a master mirror server for FL.  An ISP has offered 
rackspace and bandwidth for such a beast.  The layout I envision is this:

download.fedoralegacy.org/legacy/$releasever/SRPMS/
download.fedoralegacy.org/legacy/$releasever/SRPMS//base
download.fedoralegacy.org/legacy/$releasever/SRPMS/updates
download.fedoralegacy.org/legacy/$releasever/SRPMS/updates-testing
download.fedoralegacy.org/legacy/$releasever/SRPMS/legacy-addons
download.fedoralegacy.org/legacy/$releasever/$basearch/base
download.fedoralegacy.org/legacy/$releasever/$basearch/updates
download.fedoralegacy.org/legacy/$releasever/SRPMS/updates-testing
download.fedoralegacy.org/legacy/$releasever/$basearch/legacy-addons


where each subdir of $basearch has a directory RPMS, and a symlink SRPMS, 
which points to the correct ../../SRPMS/foo dir.  Given the 7.3 release, 
i386 arch, and the "updates" dir we would have:

download.fedoralegacy.org/legacy/7.3/i386/updates/RPMS
download.fedoralegacy.org/legacy/7.3/i386/updates/SRPMS->../../SRPMS/updates

base, updates, and legacy-addons would each be a metadata top-level, so a 
yum.conf file would look like:

[base]
name=Red Hat Linux $releasever base
baseurl=http://download.fedoralegacy.org/legacy/$releasever/$basearch/base
gpgcheck=1
 
[updates]
name=Red Hat Linux $releasever updates
baseurl=http://download.fedoralegacy.org/legacy/$releasever/$basearch/updates
gpgcheck=1

#[updates-testing]
#name=Red Hat Linux $releasever updates-testing
#baseurl=http://download.fedoralegacy.org/legacy/$releasever/$basearch/updates-testing
#gpgcheck=1
 
[legacy-addons]
name=Fedora Legacy tools for Red Hat Linux $releasever
baseurl=http://download.fedoralegacy.org/legacy/$releasever/$basearch/legacy-addons
gpgcheck=1

Same would be for the apt stuff I would assume, although I'm not familiar 
with apt setup.  I'm thinking of this from the unified metadata structure 
mindset, not apt or yum specific.

Each tree would be rsyncable, suggested rsync point would be the 
$releasever directory.  Sites like fedora.us that have a current setup 
already in place can choose to sync specific directories.  All mirrors 
should provide fedoralegacy.org the correct yum/apt conf settings specific 
to their mirror.

Thoughts?

- -- 
Jesse Keating RHCE MCSE	(http://geek.j2solutions.net)
Fedora Legacy Team	(http://www.fedora.us/wiki/FedoraLegacy)
Mondo DevTeam		(www.mondorescue.org)
GPG Public Key		(http://geek.j2solutions.net/jkeating.j2solutions.pub)

Was I helpful?  Let others know:
 http://svcs.affero.net/rm.php?r=jkeating
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAC5LZ4v2HLvE71NURAl/4AKCLX3M2AMyM2j7iScv1JQnyn1ym0ACeIP/Z
fbYtH0nrEILC/lIFeOgeDDU=
=Wvwt
-----END PGP SIGNATURE-----





More information about the fedora-legacy-list mailing list