Actually there are reasons why Microsoft systems cannot handle the changeover
as well as Linux based systems. The biggest is that the Windows API cannot
perform the conversion between local time and UTC as at some other point in
time. So, for example, if, come Monday, you look at the date of thi
On Thu, Apr 01, 2010 at 03:27:23PM +1100, Jeff Waugh wrote:
> Not sure what Linux has to do with this -- there's far more going on (with
> dates and times especially) in a complex stack of software than just the OS.
> Consider the amount of legacy software and multi-system integration involved
> in
On Thu, 1 Apr 2010 16:56:41 +1100
Nick Andrew wrote:
> On Thu, Apr 01, 2010 at 03:27:23PM +1100, Jeff Waugh wrote:
> > Not sure what Linux has to do with this -- there's far more going
> > on (with dates and times especially) in a complex stack of software
> > than just the OS. Consider the amoun
> On Thu, Apr 01, 2010 at 03:27:23PM +1100, Jeff Waugh wrote:
> > Not sure what Linux has to do with this -- there's far more going on
> > (with dates and times especially) in a complex stack of software than
> > just the OS. Consider the amount of legacy software and multi-system
> > integratio
On Thu, Apr 01, 2010 at 05:47:37PM +1100, Jeff Waugh wrote:
>
>
> > On Thu, Apr 01, 2010 at 03:27:23PM +1100, Jeff Waugh wrote:
> > > Not sure what Linux has to do with this -- there's far more going on
> > > (with dates and times especially) in a complex stack of software than
> > > just the OS.
Nick Andrew wrote:
On Thu, Apr 01, 2010 at 05:47:37PM +1100, Jeff Waugh wrote:
On Thu, Apr 01, 2010 at 03:27:23PM +1100, Jeff Waugh wrote:
Not sure what Linux has to do with this -- there's far more going on
(with dates and times especially) in a complex stack of software than
Jake Anderson wrote:
The bank may well be pretty sure that nothing will go wrong but given
the cost/benefit ratio its prudent not to take the chance that there is
one line of code somewhere or another in the many tens of millions they
have that will freak out when the clock goes backwards.
Wha
Rick Welykochy wrote:
Jake Anderson wrote:
The bank may well be pretty sure that nothing will go wrong but given
the cost/benefit ratio its prudent not to take the chance that there is
one line of code somewhere or another in the many tens of millions they
have that will freak out when the cloc
On Fri, 02 Apr 2010 13:47:32 +1100
Jake Anderson wrote:
> Rick Welykochy wrote:
> > Jake Anderson wrote:
> >
> >> The bank may well be pretty sure that nothing will go wrong but
> >> given the cost/benefit ratio its prudent not to take the chance
> >> that there is one line of code somewhere or a
