Replaced references to sunsite with references to tuxfamily.

diff --git a/README b/README
index 40a51a2b216f2b17bf3f55b9a6937853a6b17d58..f934265b3eccc8ab48a7d85b569dbc02aa5ce0f4 100644 (file)
--- a/README
+++ b/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
 through the URL 
 
-    http://chrony.sunsite.dk/
+    http://chrony.tuxfamily.org/
 
 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
 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
 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
 technical list, e.g. for discussing how new features should be
 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
-chrony-dev-subscribe@sunsite.dk
+chrony-dev-request@chrony.tuxfamily.org
 
 as applicable.
 

diff --git a/chrony.1 b/chrony.1
index 47996cc2651751f02395392ca1fa5f8e5df43498..1e0b69437a142429f1c03162fb982448cb73ddf9 100644 (file)
--- a/chrony.1
+++ b/chrony.1
@@ -55,7 +55,7 @@ session to the next)
 .BR chronyc(1),
 .BR chrony(1)
 
-.I http://chrony.sunsite.dk/
+.I http://chrony.tuxfamily.org/
 
 .SH AUTHOR
 Richard Curnow <rc@rc0.org.uk>

diff --git a/chrony.conf.5 b/chrony.conf.5
index 959c690f34c00602a45b79685f50fe95f011daad..e3b3e0082f202d2596e3dc205d2492e7f6de89ee 100644 (file)
--- a/chrony.conf.5
+++ b/chrony.conf.5
@@ -39,7 +39,7 @@ useful configuration file would look something like
 .BR chronyc(1),
 .BR chronyd(1)
 
-.I http://chrony.sunsite.dk/
+.I http://chrony.tuxfamily.org/
 
 .SH AUTHOR
 Richard Curnow <rc@rc0.org.uk>

diff --git a/chrony.lsm b/chrony.lsm
index 1e65785552325a4edce111b20a7d590aed01792b..d26cb117974c7255ac4d2795a92867f7969c82cd 100644 (file)
--- a/chrony.lsm
+++ b/chrony.lsm
@@ -17,7 +17,7 @@ Description:    A pair of programs for keeping computer clocks accurate.
 Keywords:       time NTP RFC1305 RTC adjtime
 Author:         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
                 2k chrony.lsm
 Platforms:      Linux 2.0/2.1/2.2/2.3/2.4 (x86, powerpc)

diff --git a/chrony.texi b/chrony.texi
index 428238bf605b63109ae7c4f386af56281761f8c7..38df68a3b050c0b7108564bc282c6130828e7f5e 100644 (file)
--- a/chrony.texi
+++ b/chrony.texi
@@ -109,8 +109,8 @@ the RFC did not make absolutely clear.  The core algorithms in
 
 @node Getting the software
 @subsection Getting the software
-Links on @uref{http://chrony.sunsite.dk/download.php, the
-chrony home page} describe how to obtain the software.
+Links on @uref{http://chrony.tuxfamily.org, the chrony home page}
+describe how to obtain the software.
 
 
 @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.
 
 Another source of information to try is the chrony users mailing list.  You can
-join this by sending an empty message to
-@email{chrony-users-subscribe@@sunsite.dk}.  Only subscribers can post to
+join this by sending a message with the subject subscribe to
+@email{chrony-users-request@@chrony.tuxfamily.org}.  Only subscribers can post to
 the list.
 
 When you are reporting a bug, please send me all the information you can.

diff --git a/chronyc.1 b/chronyc.1
index f74561c83d636d56dd231cc1a2bf697142273d4c..53e8d6940a6adb452887e0f3c7eba5cfb6bbf75c 100644 (file)
--- a/chronyc.1
+++ b/chronyc.1
@@ -40,13 +40,13 @@ interactively.
 1.17
 
 .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"
 .BR chronyd(8),
 .BR chrony(1)
 
-.I http://chrony.sunsite.dk/
+.I http://chrony.tuxfamily.org/
 
 .SH AUTHOR
 Richard Curnow <rc@rc0.org.uk>

diff --git a/chronyd.8 b/chronyd.8
index 52e06e239a5aad7a41f76f8d0b44a595fb3f9993..e4b94fac5346f627db37d52234530f4d16577ad5 100644 (file)
--- a/chronyd.8
+++ b/chronyd.8
@@ -102,7 +102,7 @@ This option displays \fBchronyd\fR's version number to the terminal and exits
 Version 1.17
 
 .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"
 \fBchronyd\fR is documented in detail in the documentation supplied with the

diff --git a/faq.txt b/faq.txt
index ec8d88c6cb2b1d27706fd42bff8efe0703e7d309..f11c3c80b4b1ea51c8150d1f10d934a322cdd9aa 100644 (file)
--- a/faq.txt
+++ b/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.
 
 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?
-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
 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
-<a href="mailto:chrony-announce-subscribe@sunsite.dk">chrony-announce-subscribe@sunsite.dk</a> respectively.
+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-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
-developers' mailing list.  You can subscribe by sending mail to
-<a href="mailto:chrony-dev-subscribe@sunsite.dk">chrony-dev-subscribe@sunsite.dk</a>.
+developers' mailing list.  You can subscribe by sending mail with the
+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?
 Starting from version 1.15, chrony is licensed under the GNU General Public
@@ -345,12 +346,14 @@ useful to avoid this situation.
 
 S: Development
 
-Q: Can I get the source via CVS from anywhere?
-Yes.  See <a href="http://chrony.sunsite.dk/cvs.php">http://chrony.sunsite.dk/cvs.php</a> for information.  Currently there is
-only anonymous read-only access.  I keep the master copy on my own PC, which is
-more convenient for me because I 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.
+Q: Can I get the source via CVS from anywhere?  You can get it via Git or
+in a tarball.  
+See <a href="http://chrony.tuxfamily.org/">http://chrony.tuxfamily.org</a> for
+information.  Currently there is only anonymous read-only access.  I keep
+the master copy on my own PC, which is more convenient for me because I
+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