What do you think about using the compress option? I haven't tested it before but I'm guessing you'll save some BW.
-----Original Message----- From: Scott Ullrich [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 20, 2005 4:28 PM To: support@pfsense.com Subject: Re: [pfSense Support] Anonymous access to pfSense repository Edit /home/pfsense/tools/builder_scripts/pfSense-supfile and add this: *default host=cvs.pfsense.com *default base=/home/pfsense/cvsroot *default release=cvs *default delete use-rel-suffix pfSense Then issue update_file.sh /home/pfsense/tools/builder_scripts/builder_common.sh You should now be on the new cvsup updating system. I plan on opening up the firewall in a few short minutes. On 12/20/05, Angelo Turetta <[EMAIL PROTECTED]> wrote: > Is it possible to open the pfSense repository to public r/o access? > > Downloading the full .tar.gz to update the local copy is not very > optimized. On the other side the full 'anonymous cvs' route seems prone to > security oversights & bandwidth penalty: what about going to the cvsup > route instead? > > cvsup is quite optimized for maintaining read-only slave copies of a > repository in sync. > > I could help with the setup, if that may be an incentive. > > Angelo Turetta > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
