Cool. Also please add: 211.157.103.220 As this is where my rsync connections will come from. I have added another route for now - but this will go if I reboot as I do not want to keep adding routes... RF. On 9 Mar 2007, at 8:55 PM, Lance Davis wrote: > On Fri, 9 Mar 2007, Richard Ford wrote: > >> G'Day Lance, >> >> I am not questioning your design goals or requirements. >> >> But it took me having to read many response to get a grip as to what >> is what. The fact that others may be able to do this with less >> reading or more time hacking, is not an idigtment of my competency. >> The art of good communication is brevity, accuracy and timeliness. >> >> I am not trying to score points here, but next time a major effort is >> needed, maybe the "thought writing" and desires are popped into a >> text editor first and re-read before going out in email - as opposed >> to writing as it is thought of direct to email. >> >> Anyway, I still don't know if I need a seperate IP - but I will >> assign one in any case. >> >> URL: centos-beta.candishosting.com.cn >> IP: 211.157.103.176 > > I have set you up for access > > Regards > Lance >> >> Cheers, >> RF. >> >> >> On 9 Mar 2007, at 4:44 AM, Lance Davis wrote: >> >>> On Fri, 9 Mar 2007, Richard Ford wrote: >>> >>>> So you want us to provide RSYNC services too? >>>> >>>> That is - if I only run HTTP now - I also have to offer and RSYNC >>>> server as well? >>>> >>>> This can be done, not sure of the logic - but will use more of >>>> my CPU >>>> cycles. >>>> >>>> Do we have to provide a free IP on a virtual host or just a virtual >>>> host? No matter if I use one, two, three or more aliased IP's on >>>> physical server - I always do stuff like this as a vhost for better >>>> accounting. >>>> >>>> Perhaps the centos beta stuff can be more clearly, simply and >>>> precisely explained as opposed to a dribble of half expressed >>>> emails >>>> and equally self serving responses - busy people really don't have >>>> time to work out what others are trying to say or how one persons >>>> experiences carry over to themselves. Maybe some filtering and >>>> formatting between brain and fingers/keyboard? Think of it as a >>>> requirements specification, even some rudimentary UML or use cases >>>> with event/actions would help, seriously! >>>> >>>> Failing that, I would settle for a coherent paragraph of the Queens >>>> English and a clear technical requirement spec. >>> >>> I am sorry that you are disappointed with the request others have >>> managed to make sense of it and comply. >>> >>> If you do not want to provide rsync access fine, but your mirror >>> will not be able to be a part of beta.centos.org. >>> >>> The whole point is that all the machines that are mapped on to that >>> behave similarily, otherwise it would cause no end of problems for >>> end users. >>> >>> Lance >>> >>> -- >>> uklinux.net - >>> The ISP of choice for the discerning Linux user. >>> _______________________________________________ >>> CentOS-mirror mailing list >>> CentOS-mirror at centos.org >>> http://lists.centos.org/mailman/listinfo/centos-mirror >> >> >> >> >> >> _______________________________________________ >> CentOS-mirror mailing list >> CentOS-mirror at centos.org >> http://lists.centos.org/mailman/listinfo/centos-mirror >> > > uklinux.net - > The ISP of choice for the discerning Linux user. > _______________________________________________ > CentOS-mirror mailing list > CentOS-mirror at centos.org > http://lists.centos.org/mailman/listinfo/centos-mirror