From 9ac8f64d895e34bd96b8e3af51bf93755698a0df Mon Sep 17 00:00:00 2001 From: Miroslav Lichvar Date: Fri, 2 Aug 2013 15:36:46 +0200 Subject: [PATCH] Don't mention pre 2.2 Linux kernels in documentation --- chrony.texi.in | 17 +++-------------- faq.txt | 4 ++-- 2 files changed, 5 insertions(+), 16 deletions(-) diff --git a/chrony.texi.in b/chrony.texi.in index c1d0084..d7ff1ad 100644 --- a/chrony.texi.in +++ b/chrony.texi.in @@ -125,9 +125,7 @@ different quirks in its behaviour. The software is known to work in the following environments: @itemize @bullet -@item Linux on i386, x86_64 and PowerPC architectures. The software is known -to work on Linux 2.0.x and newer. Prior to 2.0.31, the real time clock can't -be used. +@item Linux 2.2 and newer @item NetBSD @item BSD/386 @@ -826,18 +824,10 @@ compiled into the kernel). An estimate is made of the RTC error at a particular RTC second, and the rate at which the RTC gains or loses time relative to true time. -The RTC is fully supported in 2.2, 2.4 and 2.6 kernels. - -On 2.6 kernels, if your motherboard has a HPET, you need to enable the +On 2.6 and later kernels, if your motherboard has a HPET, you need to enable the @samp{HPET_EMULATE_RTC} option in your kernel configuration. Otherwise, chrony will not be able to interact with the RTC device and will give up using it. -For kernels in the 2.0 series prior to 2.0.32, the kernel was set up to -trim the RTC every 11 minutes. This would be disasterous for -@code{chronyd} -- there is no reliable way of synchronising with this -trimming. For this reason, @code{chronyd} only supports the RTC in 2.0 -kernels from v2.0.32 onwards. - When the computer is powered down, the measurement histories for all the NTP servers are saved to files (if the @code{dumponexit} directive is specified in the configuration file), and the RTC tracking information @@ -2637,8 +2627,7 @@ conditions apply: @enumerate 1 @item -You are running Linux version 2.2.x or 2.4.x (for any value of x), or v2.0.x -with x>=32. +You are running Linux version 2.2.x or later. @item You have compiled the kernel with extended real-time clock support diff --git a/faq.txt b/faq.txt index 93ee232..d9ed6dd 100644 --- a/faq.txt +++ b/faq.txt @@ -68,7 +68,7 @@ support hardware reference clocks to your computer, then xntpd will work fine. Apart from not supporting hardware clocks, chrony will work fine too. If your computer connects to the 'net for 5 minutes once a day (or something -like that), or you turn your (Linux v2.0) computer off when you're not using +like that), or you turn your Linux computer off when you're not using it, or you want to use NTP on an isolated network with no hardware clocks in sight, chrony will work much better for you. @@ -271,7 +271,7 @@ The program needs to see the definitions of structures used to interact with the real time clock (via /dev/rtc) and with the adjtimex() system call. Sadly this has led to a number of compilation problems with newer kernels which have been increasingly hard to fix in a way that makes the code compilable on all -Linux kernel versions (from 2.0 up anyway, I doubt 1.x still works.) Hopefully +Linux kernel versions. Hopefully the situation will not deteriorate further with future kernel versions. Q: I get "Could not open /dev/rtc, Device or resource busy" in my syslog file.