Ron Leach wrote:
> And London is going to shift from UTC to its local daylight saving time,
> British summer Time, BST, sometime in the next week or so.
Pendantically speaking, not really. We were on GMT and are now on BST. UTC
is invariant, and although it just so happens that GMT is the same as
On 3/22/2014 11:51 PM, Chris Bannister wrote:
On Fri, Mar 21, 2014 at 11:10:32PM -0400, Jerry Stuckle wrote:
On 3/21/2014 10:08 PM, John Hasler wrote:
Jerry Stuckle writes:
The time needs to be accurate
TAI is accurate. UTC is fudged. The Earth is not a clock. BTW GPS
time ignores leap se
On Fri, Mar 21, 2014 at 11:10:32PM -0400, Jerry Stuckle wrote:
> On 3/21/2014 10:08 PM, John Hasler wrote:
> >Jerry Stuckle writes:
> >>The time needs to be accurate
> >
> >TAI is accurate. UTC is fudged. The Earth is not a clock. BTW GPS
> >time ignores leap seconds. It's what scientists most
On 3/22/2014 9:58 AM, Martin G. McCormick wrote:
Jerry Stuckle writes:
That wouldn't work well. Remember, computers are not the only ones which
use UTC - in fact they are the most imprecise. There are many clocks
around
the world which are synchronized with UTC via radio, i.e. WWV/WWVH in the
Un
Jerry Stuckle writes:
> That wouldn't work well. Remember, computers are not the only ones which
> use UTC - in fact they are the most imprecise. There are many clocks
> around
> the world which are synchronized with UTC via radio, i.e. WWV/WWVH in the
> United States, CHU in Canada, and other sta
On 3/21/2014 10:14 PM, John Hasler wrote:
http://en.wikipedia.org/wiki/Leap_second#Proposal_to_abolish_leap_seconds
This is hardly the first time this has been proposed. I remember it way
back in the 60's.
There are advantages and disadvantages to it. So far the disadvantages
have outwei
On 3/21/2014 10:08 PM, John Hasler wrote:
Jerry Stuckle writes:
The time needs to be accurate
TAI is accurate. UTC is fudged. The Earth is not a clock. BTW GPS
time ignores leap seconds. It's what scientists most often use for
precise timing.
Not all of them. Many use UTC. UTC is read
http://en.wikipedia.org/wiki/Leap_second#Proposal_to_abolish_leap_seconds
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.de
Jerry Stuckle writes:
> The time needs to be accurate
TAI is accurate. UTC is fudged. The Earth is not a clock. BTW GPS
time ignores leap seconds. It's what scientists most often use for
precise timing.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
--
To UNSUBSCRIBE, email to debian-
On 3/21/2014 5:35 PM, John Hasler wrote:
http://en.wikipedia.org/wiki/International_Atomic_Time
http://en.wikipedia.org/wiki/Coordinated_Universal_Time
http://en.wikipedia.org/wiki/Leap_second
More TAI seconds have accumulated since 1972 than have UTC seconds
because the Earth is slowing down an
I chose the posix time for Europe/London and the seconds
are in exact step with local time seconds.
Martin
Ron Leach writes:
> On 21/03/2014 20:21, John Hasler wrote:
>
>
> Other way around. TAI does *not* include leap-seconds. It is a
> continuous stream of numbered seconds w
On Friday 21 March 2014 20:43:37 Ron Leach wrote:
> And, like the OP, I don't want to miss the start of radio
> programmes because the time isn't correct, aligned, or understood.
Never listen to the BBC then.
Lisi
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject
On Friday 21 March 2014 20:02:38 Ron Leach wrote:
> The OP might want to keep in mind
> that the time he thinks he has set his recording to start may be 35
> seconds adrift from when the broadcaster might start. At least, he
> might want to check what time he uses, and what time the
> broadcaster
http://en.wikipedia.org/wiki/International_Atomic_Time
http://en.wikipedia.org/wiki/Coordinated_Universal_Time
http://en.wikipedia.org/wiki/Leap_second
More TAI seconds have accumulated since 1972 than have UTC seconds
because the Earth is slowing down and so to keep UTC in sync with the
Earth it
On 21/03/2014 20:21, John Hasler wrote:
Other way around. TAI does *not* include leap-seconds. It is a
continuous stream of numbered seconds with no gaps and no insertions.
UTC *does* include leap seconds. It is TAI adjusted to stay within one
second of Earth rotation time. Leap seconds acco
Ron Leach writes:
> Interesting. The readme in Wheezy states that TAI includes 'leap
> seconds' (the extra seconds added - every so often, a year or so - to
> compensate for variations in Earth's rotation) and implies that the
> UTC time basis does *not* include the leap seconds. I wonder if that
On 21/03/2014 02:58, Don Armstrong wrote:
[,,,] due to the 35 second difference between TAI and UTC. (The latter
approximates UT1 (earth revolution about its axis), and the former is
absolute time in SI seconds).
You can read about it in /usr/share/doc/tzdata/README.Debian.
Interesting. The
Le 21/03/2014 17:18, Brian a écrit :
> On Fri 21 Mar 2014 at 14:32:33 +0100, Slavko wrote:
>
>> There was possible to configure to use UTC or local time as
>> system time, but this make sense only for multiboot with system(s),
>> which uses local time only (eg. Windows) and now i cannot find this
>
Ahoj,
Dňa Fri, 21 Mar 2014 16:18:22 + Brian
napísal:
> On Fri 21 Mar 2014 at 14:32:33 +0100, Slavko wrote:
>
> > There was possible to configure to use UTC or local time as
> > system time, but this make sense only for multiboot with system(s),
> > which uses local time only (eg. Windows) a
On Fri 21 Mar 2014 at 14:32:33 +0100, Slavko wrote:
> There was possible to configure to use UTC or local time as
> system time, but this make sense only for multiboot with system(s),
> which uses local time only (eg. Windows) and now i cannot find this
> setting, because it was taken away from /e
On a properly-working unix system, the hardware clock is
set to UTC. In theory, every unix system in the world has a
hardware clock that reads the same value at the same time. The
localtime file is a set of rules that adjusts your UTC clock
value to whatever local wall clock time should be.
Ahoj,
Dňa Fri, 21 Mar 2014 10:57:08 + Ron Leach
napísal:
> On 21/03/2014 09:38, Lisi Reisz wrote:
> >
> > It is standard "good practice" to keep system time ("hardware
> > clock") at UTC, and desktop time can be local time if you wish.
> >
>
> Hadn't realised any of this, so thank you. If
On 21/03/2014 09:38, Lisi Reisz wrote:
It is standard "good practice" to keep system time ("hardware clock")
at UTC, and desktop time can be local time if you wish.
Hadn't realised any of this, so thank you. If 'system time' and
'desktop time' differ - such as is suggested - what 'timestamp
On Friday 21 March 2014 09:05:37 Ron Leach wrote:
> >> I want to record some radio programs and DST and BST don't start
> >> and stop at the same times.
> >
> > The way you do this is you start whatever you're using to record
> > the programs with TZ="Europe/London" instead of changing
> > /etc/loc
On 21/03/2014 02:58, Don Armstrong wrote,
very interestingly:
On Thu, 20 Mar 2014, Martin G. McCormick wrote:
That's when I discovered that there are 3
Londons and 3 Chicagos.
That's due to the 35 second difference between TAI and UTC. (The latter
approximates UT1 (earth revolution about its
On Thu, 20 Mar 2014, Martin G. McCormick wrote:
> What is the difference between the 3 versions of various time zone
> files? I live in the US-Central time zone and wanted to set a debian
> system to London time which means replacing /etc/localtime to the file
> that coresponds to London. That's wh
What is the difference between the 3 versions of various
time zone files? I live in the US-Central time zone and wanted
to set a debian system to London time which means replacing
/etc/localtime to the file that coresponds to London. That's
when I discovered that there are 3 Londons and 3 C
27 matches
Mail list logo
