Server name: ftp.heanet.ie Server IPv4 Address: 193.1.219.100 Server IPv6 Address: 2001:770:18:2::1:100 Server specs: 2 * Intel Xeon P4 2 Ghz CPUs, 12 GB RAM Bandwidth: 1 Gbps User connection limit: none Server location: Dublin, Ireland Contact name: Mirror Team, mirrors@heanet.ie Reproducible: Always Steps to Reproduce: 1. 2. 3. The server is available over IPv4 and IPv6 at: http://ftp.heanet.ie/mirrors/gentoo.org http://ftp.heanet.ie/mirrors/gentoo.org-portage ftp://ftp.heanet.ie/mirrors/gentoo.org ftp://ftp.heanet.ie/mirrors/gentoo.org-portage rsync://ftp.heanet.ie/mirrors/gentoo.org rsync://ftp.heanet.ie/mirrors/gentoo.org-portage
We are about to split the server which is mirroring into two (onw will be an rsync client keeping in sync with things, the other will serve rsync, ftp and http to the general community). The IPv4 address of the server which will need rsync access to a master will be 193.1.219.88, the IPv6 address will be 2001:770:18:2:206:5bff:fe8c:3f37 (this is an EUI-64 address, which will be the default source address of any connections). BTW, I understand the project is run by people in their own time, but is there any ETA for acceptance (or rejection) of this mirror?
IPV4 mirror added into rsync.europe.gentoo.org rotation. there is no subdomain for ie.gentoo.org, i will have to wait for cshields/klieber to return to add the IE specific subdomain. please set your mirror to sync to rsync1.us.gentoo.org. i will have to get back to you about the IPV6 when i have knowledge of how to setup access. thanks your contribution
Hi, Thanks for that. If you are just listing us as a mirror, then you dont need to do anything for IPv6 - it should work ok for people with it setup already. If you are looking to add a DNS record, then you can either point a CNAME record at our ftp.heanet.ie, or if you are adding an A record at the IP address, you can also add an AAAA record pointing at the : separated v6 address. Perhaps you can clear something up for me - the rsync site you've given me access to exports gentoo-portage. Some other sites (like ibiblio) make additional trees such as gentoo and gentoo-x86-portage available. Should I be making these available somehow? Brian.
gentoo-x86-portage is an old name for the same tree. It's maintained for historical reasons. If you want to add it, you can simply duplicate your existing rsyncd.conf entry. However, at this point, very few people still use it, so it's also safe to leave it out. The files retrieved via gentoo-portage and gentoo-x86-portage are identical.
issue resolved. happy mirroring.
Thanks for the info on gentoo-x86-portage. Sorry to be a pest, but could I re-submit a part of my previous question: What is the relationship between publically available rsync targets like rsync://ftp.ibiblio.org/gentoo and gentoo-portage? In gentoo-portage, I see a wide variety of package trees. In gentoo, I see four directories, distfiles experimental releases snapshots Are these useful to the community? We've been mirroring both targets from various points, and if one is superflous, I'll drop it. If not, should I be able to see a rsync::gentoo target in addtion to gentoo-portage on your rsync server? Thanks again, Brian.
ah -- ok, I didn't read your first question carefully enough. the 'gentoo' module that you see on ibiblio and some other servers is actually a mirror of our source files. Gentoo has two types of mirrors: rsync mirrors, which mirror the portage tree (ebuilds, etc.) and source mirrors, which mirror the source tarballs of the actual programs. If you'd also like to be a source mirror, that would be outstanding. You don't have to mirror the sources via rsync, but you're welcome to if you like. We do ask that you support either http or ftp (or both) for mirroring source tarballs. More info on becoming a source mirror is available here: http://www.gentoo.org/doc/en/source_mirrors.xml No need to file a separate bug if you want to become a source mirror -- just post a comment to that effect on this bug and we'll get that set up. Thanks again.
Just to clarify my previous comment: You do have to mirror the source tarballs via rsync. You do not, however, have to make the sources avaialble publicly via rsync. Most of our mirrors use rsync to get new tarballs from upstream but only use ftp and/or http to serve them out to users since ftp/http are far less resource-intensive than rsync.
Thanks for the quick response - our mirror is rsyncing both targets now. We make everything on our mirror server available via rsync, ftp and http, and you are welcome to advertise them. The rsync URLs are: rsync://ftp.heanet.ie/pub/gentoo rsync://ftp.heanet.ie/pub/gentoo-portage If you want, you can use a similar tree in the http/ftp urls (though the ones I mentioned earlier are also good): http://ftp.heanet.ie/pub/gentoo http://ftp.heanet.ie/pub/gentoo-portage ftp://ftp.heanet.ie/pub/gentoo ftp://ftp.heanet.ie/pub/gentoo-portage Best regards, Brian.
source distfile mirrors added to mirrors.xml. thanks for helping out!
rsync server removed from europe.gentoo.org rotation, since no response. rsync: failed to connect to 193.1.219.88: No route to host rsync error: error in socket IO (code 10) at clientserver.c(88) please file a new bug if you wish to be readded as an rsync server.
