Date: Fri, 2 Jun 2006 22:14:29 -0400 From: Randy Pratt <bsd-unix@earthlink.net> To: freebsd-questions@freebsd.org Subject: Re: How to get networker backup software Message-ID: <20060602221429.79e9f748.bsd-unix@earthlink.net> In-Reply-To: <dd4da0390606021501i641a0b4dwb8a5a93ceb74d7d8@mail.gmail.com> References: <dd4da0390606021249m58bfbb16m8f391d3373e90024@mail.gmail.com> <20060602164309.9863f9d8.bsd-unix@earthlink.net> <dd4da0390606021501i641a0b4dwb8a5a93ceb74d7d8@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2 Jun 2006 19:01:38 -0300 "Donald Teed" <donald.teed@gmail.com> wrote: > As far as I know, the security issues are moot. The note > I remember seeing said that the default configuration > was problematic. If our backup server is behind a firewall, > and we always config things after installing, I can't > see how the security issue is relevant enough to rip > it out of ports. It is far better to have a security issue > awaiting resolution than to have zero backup capability. > > The ports skeleton we have is on one machine and > shared by NFS to the rest. It is updated nightly so > the old one is gone. We do have the tarball > in distfiles, but I don't see a Makefile, etc. > > How do I find it from CVS source? Is there a pointer on > where to find that? You could get a complete tree just before the port was removed by setting a date in a cvsup file. Its been awhile since I've done this but here's a modified example from an old file I still had: *default host=cvsup4.FreeBSD.org (or whatever) *default base=/usr/oldtree *default prefix=/home/oldtree *default release=cvs *default delete use-rel-suffix *default date=2006.03.31.00.00.00 *default compress ports-all I think that date is about 8 hours before the ports were removed from the tree but you might want to check the dates of any other ports you might need to be sure the date is correct for what you need. You can check these with cvsweb: http://www.freebsd.org/cgi/cvsweb.cgi/ Note that the base and prefix are different so that you don't clobber your existing ports tree. Choose something appropriate for your situation. Instead of using "ports-all", you might save some bandwidth by only selecting the ports modules you need. They are listed in: /usr/share/examples/cvsup/ports-supfile You would have selected entries in your supfile like: ports-base ports-sysutils After that, just cvsup using the new supfile. That should get what is needed and then you'll be able to add them to your NFS tree. It sounds like you're quite familar with these ports. Perhaps if you can get them security patched you might consider becoming the maintainer for the ports and get them back in the tree. Perhaps this will get you closer to where you need to be. If anyone spots anything I missed, be sure to comment. Randy --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060602221429.79e9f748.bsd-unix>