[RESOLVED] Re: How to get networker backup software
donald.teed at gmail.com
Mon Jun 5 12:55:18 PDT 2006
The trick of doing a ports cvsup from back
in time worked. We have a working networker client again!
I'm even more concerned that the client version
is going to go stale. I don't know how the package
was made for BSD, and I'm not sure if it
is legally possibly to port the current versions
of the networker client over.
Thanks for the assistance, Randy...
On 6/2/06, Randy Pratt <bsd-unix at earthlink.net> wrote:
> On Fri, 2 Jun 2006 19:01:38 -0300
> "Donald Teed" <donald.teed at 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
> 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:
> 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:
> You would have selected entries in your supfile like:
> 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.
> freebsd-questions at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
More information about the freebsd-questions