Replaced references to sunsite with references to tuxfamily.
This commit is contained in:
parent
8e23110aec
commit
27cfc02468
8 changed files with 32 additions and 28 deletions
13
README
13
README
|
@ -84,7 +84,7 @@ ready-formatted plain text (chrony.txt) in the distribution.
|
||||||
There is also information available on the chrony web pages, accessible
|
There is also information available on the chrony web pages, accessible
|
||||||
through the URL
|
through the URL
|
||||||
|
|
||||||
http://chrony.sunsite.dk/
|
http://chrony.tuxfamily.org/
|
||||||
|
|
||||||
What can chrony not do?
|
What can chrony not do?
|
||||||
=======================
|
=======================
|
||||||
|
@ -97,9 +97,9 @@ Where are new versions announced?
|
||||||
|
|
||||||
There is a low volume mailing list where new versions and other
|
There is a low volume mailing list where new versions and other
|
||||||
important news relating to chrony is announced. You can join this list
|
important news relating to chrony is announced. You can join this list
|
||||||
by sending mail to
|
by sending mail with the subject "subscribe" to
|
||||||
|
|
||||||
chrony-announce-subscribe@sunsite.dk
|
chrony-announce-request@chrony.tuxfamily.org
|
||||||
|
|
||||||
These messages will be copied to chrony-users (see below). I also try
|
These messages will be copied to chrony-users (see below). I also try
|
||||||
to announce new versions on Freshmeat (http://freshmeat.net/).
|
to announce new versions on Freshmeat (http://freshmeat.net/).
|
||||||
|
@ -116,11 +116,12 @@ mentioned above. chrony-users is a users' discussion list, e.g. for
|
||||||
general questions and answers about using chrony. chrony-dev is a more
|
general questions and answers about using chrony. chrony-dev is a more
|
||||||
technical list, e.g. for discussing how new features should be
|
technical list, e.g. for discussing how new features should be
|
||||||
implemented, exchange of information between developers etc. To
|
implemented, exchange of information between developers etc. To
|
||||||
subscribe to either of these lists, send an empty message to
|
subscribe to either of these lists, send amessage with the subject
|
||||||
|
"subscribe" to
|
||||||
|
|
||||||
chrony-users-subscribe@sunsite.dk
|
chrony-users-request@chrony.tuxfamily.org
|
||||||
or
|
or
|
||||||
chrony-dev-subscribe@sunsite.dk
|
chrony-dev-request@chrony.tuxfamily.org
|
||||||
|
|
||||||
as applicable.
|
as applicable.
|
||||||
|
|
||||||
|
|
2
chrony.1
2
chrony.1
|
@ -55,7 +55,7 @@ session to the next)
|
||||||
.BR chronyc(1),
|
.BR chronyc(1),
|
||||||
.BR chrony(1)
|
.BR chrony(1)
|
||||||
|
|
||||||
.I http://chrony.sunsite.dk/
|
.I http://chrony.tuxfamily.org/
|
||||||
|
|
||||||
.SH AUTHOR
|
.SH AUTHOR
|
||||||
Richard Curnow <rc@rc0.org.uk>
|
Richard Curnow <rc@rc0.org.uk>
|
||||||
|
|
|
@ -39,7 +39,7 @@ useful configuration file would look something like
|
||||||
.BR chronyc(1),
|
.BR chronyc(1),
|
||||||
.BR chronyd(1)
|
.BR chronyd(1)
|
||||||
|
|
||||||
.I http://chrony.sunsite.dk/
|
.I http://chrony.tuxfamily.org/
|
||||||
|
|
||||||
.SH AUTHOR
|
.SH AUTHOR
|
||||||
Richard Curnow <rc@rc0.org.uk>
|
Richard Curnow <rc@rc0.org.uk>
|
||||||
|
|
|
@ -17,7 +17,7 @@ Description: A pair of programs for keeping computer clocks accurate.
|
||||||
Keywords: time NTP RFC1305 RTC adjtime
|
Keywords: time NTP RFC1305 RTC adjtime
|
||||||
Author: rc@rc0.org.uk (Richard Curnow)
|
Author: rc@rc0.org.uk (Richard Curnow)
|
||||||
Maintained-by: rc@rc0.org.uk (Richard Curnow)
|
Maintained-by: rc@rc0.org.uk (Richard Curnow)
|
||||||
Primary-site: sunsite.unc.edu /pub/Linux/system/admin/time
|
Primary-site: chrony.tuxfamily.org
|
||||||
295k chrony-1.18.tar.gz
|
295k chrony-1.18.tar.gz
|
||||||
2k chrony.lsm
|
2k chrony.lsm
|
||||||
Platforms: Linux 2.0/2.1/2.2/2.3/2.4 (x86, powerpc)
|
Platforms: Linux 2.0/2.1/2.2/2.3/2.4 (x86, powerpc)
|
||||||
|
|
|
@ -109,8 +109,8 @@ the RFC did not make absolutely clear. The core algorithms in
|
||||||
|
|
||||||
@node Getting the software
|
@node Getting the software
|
||||||
@subsection Getting the software
|
@subsection Getting the software
|
||||||
Links on @uref{http://chrony.sunsite.dk/download.php, the
|
Links on @uref{http://chrony.tuxfamily.org, the chrony home page}
|
||||||
chrony home page} describe how to obtain the software.
|
describe how to obtain the software.
|
||||||
|
|
||||||
|
|
||||||
@node Platforms
|
@node Platforms
|
||||||
|
@ -279,8 +279,8 @@ children, my job, and indeed other free/open source software projects.
|
||||||
However, I do intend to look into problems when time allows.
|
However, I do intend to look into problems when time allows.
|
||||||
|
|
||||||
Another source of information to try is the chrony users mailing list. You can
|
Another source of information to try is the chrony users mailing list. You can
|
||||||
join this by sending an empty message to
|
join this by sending a message with the subject subscribe to
|
||||||
@email{chrony-users-subscribe@@sunsite.dk}. Only subscribers can post to
|
@email{chrony-users-request@@chrony.tuxfamily.org}. Only subscribers can post to
|
||||||
the list.
|
the list.
|
||||||
|
|
||||||
When you are reporting a bug, please send me all the information you can.
|
When you are reporting a bug, please send me all the information you can.
|
||||||
|
|
|
@ -40,13 +40,13 @@ interactively.
|
||||||
1.17
|
1.17
|
||||||
|
|
||||||
.SH BUGS
|
.SH BUGS
|
||||||
To report bugs, please contact the author and/or visit \fIhttp://chrony.sunsite.dk/\fR
|
To report bugs, please contact the author and/or visit \fIhttp://chrony.tuxfamily.org
|
||||||
|
|
||||||
.SH "SEE ALSO"
|
.SH "SEE ALSO"
|
||||||
.BR chronyd(8),
|
.BR chronyd(8),
|
||||||
.BR chrony(1)
|
.BR chrony(1)
|
||||||
|
|
||||||
.I http://chrony.sunsite.dk/
|
.I http://chrony.tuxfamily.org/
|
||||||
|
|
||||||
.SH AUTHOR
|
.SH AUTHOR
|
||||||
Richard Curnow <rc@rc0.org.uk>
|
Richard Curnow <rc@rc0.org.uk>
|
||||||
|
|
|
@ -102,7 +102,7 @@ This option displays \fBchronyd\fR's version number to the terminal and exits
|
||||||
Version 1.17
|
Version 1.17
|
||||||
|
|
||||||
.SH BUGS
|
.SH BUGS
|
||||||
To report bugs, please contact the author and/or visit \fIhttp://chrony.sunsite.dk/\fR
|
To report bugs, please contact the author and/or visit \fIhttp://chrony.tuxfamily.org/\fR
|
||||||
|
|
||||||
.SH "SEE ALSO"
|
.SH "SEE ALSO"
|
||||||
\fBchronyd\fR is documented in detail in the documentation supplied with the
|
\fBchronyd\fR is documented in detail in the documentation supplied with the
|
||||||
|
|
27
faq.txt
27
faq.txt
|
@ -45,18 +45,19 @@ I am aware of packages for Debian, Mandrake and Redhat. I am not personally
|
||||||
involved with how these are built or distributed.
|
involved with how these are built or distributed.
|
||||||
|
|
||||||
Q: Where is the home page?
|
Q: Where is the home page?
|
||||||
It is currently at <a href="http://chrony.sunsite.dk/">http://chrony.sunsite.dk/</a>.
|
It is currently at <a href="http://chrony.tuxfamily.org/">http://chrony.tuxfamily.org/</a>.
|
||||||
|
|
||||||
Q: Is there a mailing list?
|
Q: Is there a mailing list?
|
||||||
Yes, it's currently at chrony-users@sunsite.dk. There is a low-volume
|
Yes, it's currently at chrony-users@chrony.tuxfamily.org. There is a low-volume
|
||||||
list called chrony-announce which is just for announcements of new releases or
|
list called chrony-announce which is just for announcements of new releases or
|
||||||
similar matters of high importance. You can join the lists by sending a
|
similar matters of high importance. You can join the lists by sending a
|
||||||
message to <a href="mailto:chrony-users-subscribe@sunsite.dk">chrony-users-subscribe@sunsite.dk</a> or
|
message with the subject subscribe to <a href="mailto:chrony-users-request@chrony.tuxfamily.org">chrony-users-request@chrony.tuxfamily.org</a> or
|
||||||
<a href="mailto:chrony-announce-subscribe@sunsite.dk">chrony-announce-subscribe@sunsite.dk</a> respectively.
|
<a href="mailto:chrony-announce-request@chrony.tuxfamily.org">chrony-announce-request@chrony.tuxfamily.org</a> respectively.
|
||||||
|
|
||||||
For those who want to contribute to the development of chrony, there is a
|
For those who want to contribute to the development of chrony, there is a
|
||||||
developers' mailing list. You can subscribe by sending mail to
|
developers' mailing list. You can subscribe by sending mail with the
|
||||||
<a href="mailto:chrony-dev-subscribe@sunsite.dk">chrony-dev-subscribe@sunsite.dk</a>.
|
subject subscribe to
|
||||||
|
<a href="mailto:chrony-dev-request@chrony.tuxfamily.org">chrony-dev-request@chrony.tuxfamily.org</a>.
|
||||||
|
|
||||||
Q: What licence is applied to chrony?
|
Q: What licence is applied to chrony?
|
||||||
Starting from version 1.15, chrony is licensed under the GNU General Public
|
Starting from version 1.15, chrony is licensed under the GNU General Public
|
||||||
|
@ -345,12 +346,14 @@ useful to avoid this situation.
|
||||||
|
|
||||||
S: Development
|
S: Development
|
||||||
|
|
||||||
Q: Can I get the source via CVS from anywhere?
|
Q: Can I get the source via CVS from anywhere? You can get it via Git or
|
||||||
Yes. See <a href="http://chrony.sunsite.dk/cvs.php">http://chrony.sunsite.dk/cvs.php</a> for information. Currently there is
|
in a tarball.
|
||||||
only anonymous read-only access. I keep the master copy on my own PC, which is
|
See <a href="http://chrony.tuxfamily.org/">http://chrony.tuxfamily.org</a> for
|
||||||
more convenient for me because I don't have to connect to the Internet to do
|
information. Currently there is only anonymous read-only access. I keep
|
||||||
CVS operations on the files. So for now, there is no read-write access for
|
the master copy on my own PC, which is more convenient for me because I
|
||||||
other developers. Please email me your patches + documentation instead.
|
don't have to connect to the Internet to do CVS operations on the files.
|
||||||
|
So for now, there is no read-write access for other developers. Please
|
||||||
|
email me your patches + documentation instead.
|
||||||
|
|
||||||
S: Linux-specific issues
|
S: Linux-specific issues
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue