Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 13 Jan 2009 07:04:11 -0500
From:      Jerry <gesbbb@yahoo.com>
To:        freebsd-questions@freebsd.org
Subject:   Re: local copy of handbook
Message-ID:  <20090113070411.1e741238@scorpio>
In-Reply-To: <20081229105904.523e3494.bsd-unix@embarqmail.com>
References:  <b10011eb0812282046j7b784d82q492c8b10cb46db06@mail.gmail.com> <20081229124558.43cefc56@gumby.homeunix.com> <200812292039.43242.masoom.shaikh@gmail.com> <20081229105904.523e3494.bsd-unix@embarqmail.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
--Sig_/BFl=W6T.+y0z=pA+IMc/1jW
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Mon, 29 Dec 2008 10:59:04 -0500
Randy Pratt <bsd-unix@embarqmail.com> wrote:

>You might consider using Docsnap.  This allows you to maintain all
>the FreeBSD documentation with a minimum of effort.
>
>Docsnap is an rsync repository for easy updating of installed
>FreeBSD documentation (/usr/share/doc).
>
>The first run may take longer but subsequent updates take very
>little time.  Only the differences in the documents are transferred.
>That is the main advantage but you also do not need to install ports
>with hefty overhead to build documents.
>
>Rsync is only utility required (/usr/ports/net/rsync). Typical usage:
>
>  # rsync -rltvz docsnap.sk.FreeBSD.org::docsnap /usr/share/doc/
>
>For more information see http://docsnap.sk.freebsd.org/ and possibly
>the rsync manual page.

I reported last week that this was not working. It still fails with the
following error message:

~ # rsync -rltvz docsnap.sk.FreeBSD.org::docsnap /usr/share/doc/
rsync: failed to connect to docsnap.sk.FreeBSD.org: Connection refused
(61) rsync error: error in socket IO (code 10) at clientserver.c(124)
[receiver=3D3.0.5]

I was under the impression that someone was looking into it. Is there
any estimated time for the link to be fixed?


--=20
Jerry
gesbbb@yahoo.com

Strategy:
	A long-range plan whose merit cannot be evaluated until sometime
	after those creating it have left the organization.

--Sig_/BFl=W6T.+y0z=pA+IMc/1jW
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAklsg0QACgkQBvaKIJWWCO0kXwCbBOTZrIySyF5uLdONEG0Hp2Q4
18wAnighaaJh0wMvzRfCfG2Pj6sukK5C
=atx9
-----END PGP SIGNATURE-----

--Sig_/BFl=W6T.+y0z=pA+IMc/1jW--



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20090113070411.1e741238>