On 05/02/2011 09:48 AM, Thomas Bächler wrote:
Am 02.05.2011 14:43, schrieb Tom Gundersen:
On Mon, May 2, 2011 at 10:52 AM, Thomas Bächler wrote:
Am 29.04.2011 02:33, schrieb Tom Gundersen:
Hi guys,
A new initscripts package is in testing, please test and signoff.
The only change since -1 is
On 30-04-2011 00:51, Loui Chang wrote:
> Sounds like a hardware problem then. Maybe the bios should tell the OS
> if the clock is in localtime or UTC. ;)
Not really, the real time clock is a clock, it is supposed to keep the
time always moving forward in the most accurate way possible, ideally it
On Fri 29 Apr 2011 23:00 +0200, Tom Gundersen wrote:
> On Fri, Apr 29, 2011 at 8:41 PM, David Rosenstrauch wrote:
> > Can someone pls clarify what exactly is broken about localtime? I've been
> > using it for years without any (noticable) issue. I'll be happy to switch
> > over if I need to, but
On Fri, Apr 29, 2011 at 10:44 PM, Denis A. Altoé Falqueto
wrote:
> Yeah, you are right. At first sight (or maybe an oversight...) I've
> got the impression of it being unsupported from now on. But rereading
> the thread made that clear. Maybe that could be made more explicit.
Yes, it appears this
On Fri, Apr 29, 2011 at 8:41 PM, David Rosenstrauch wrote:
> Can someone pls clarify what exactly is broken about localtime? I've been
> using it for years without any (noticable) issue. I'll be happy to switch
> over if I need to, but I'd like to understand the problem(s) first.
There are some
On Fri, Apr 29, 2011 at 5:38 PM, Tom Gundersen wrote:
> On Fri, Apr 29, 2011 at 10:16 PM, Heiko Baums wrote:
>> [...] if localtime isn't
>> supported anymore.
>
> Sorry to be repeating myself: we are not considering dropping support
> for localtime.
Yeah, you are right. At first sight (or maybe
On Fri, Apr 29, 2011 at 10:16 PM, Heiko Baums wrote:
> [...] if localtime isn't
> supported anymore.
Sorry to be repeating myself: we are not considering dropping support
for localtime.
We are just pointing out that it is a bad idea to use it (it has
always been a bad idea, nothing has changed,
On Fri, Apr 29, 2011 at 5:11 PM, Thomas Bächler wrote:
> Am 29.04.2011 15:36, schrieb Heiko Baums:
>> And I say my opinion, at least if I see that there could be
>> regressions or serious issues.
>
> If I remember it right, the only changes were the default value and
> comment in rc.conf.
Correct
2011/4/29 Heiko Baums :
> Am Fri, 29 Apr 2011 17:11:22 +0200
> schrieb Thomas Bächler :
>
>> If I remember it right, the only changes were the default value and
>> comment in rc.conf.
>
> Maybe, and it's alright. But as it wasn't released, yet, I just wanted
> to note that a lot of people could get
Am Fri, 29 Apr 2011 17:11:22 +0200
schrieb Thomas Bächler :
> If I remember it right, the only changes were the default value and
> comment in rc.conf.
Maybe, and it's alright. But as it wasn't released, yet, I just wanted
to note that a lot of people could get problems if localtime isn't
support
Am Fri, 29 Apr 2011 11:18:16 -0300
schrieb Ángel Velásquez :
> Ok are you freaking joking on me? Why we have to worry about other OS?
> if they do the wrong things, then report it to them, we don't have to
> eat a hundreds of bugs, just because you like a crappy os just for
> game.
If you had rea
On 04/28/2011 11:22 PM, C Anthony Risinger wrote:
setting the hardware clock to localtime is 100% broken and the links
provided in the original announcement explain the ramifications
clearly ... at least i thought there were links somewhere ... wtf,
where did i see them? it was an arch-related m
Am 29.04.2011 15:36, schrieb Heiko Baums:
> And I say my opinion, at least if I see that there could be
> regressions or serious issues.
If I remember it right, the only changes were the default value and
comment in rc.conf.
signature.asc
Description: OpenPGP digital signature
2011/4/29 Heiko Baums :
> Am Fri, 29 Apr 2011 07:07:58 -0400
> schrieb Matthew Gyurgyik :
>
>> I'm with Thomas here. If it bugs you that much submit some patches.
>> It seems as if you always have an opinion, but rarely have a solution
>> and/or patches.
>
> And I say my opinion, at least if I see
Am Fri, 29 Apr 2011 07:07:58 -0400
schrieb Matthew Gyurgyik :
> I'm with Thomas here. If it bugs you that much submit some patches.
> It seems as if you always have an opinion, but rarely have a solution
> and/or patches.
And I say my opinion, at least if I see that there could be
regressions or
Hi all,
I'll try to answer all the comments in one go:
On Fri, Apr 29, 2011 at 2:43 AM, Heiko Baums wrote:
> Am Fri, 29 Apr 2011 02:33:57 +0200
> schrieb Tom Gundersen :
>
>> * We now strongly discourage the use of HWCLOCK="localtime", as this
>> may lead to several known and unfixable bugs
>
>
On 04/29/2011 06:46 AM, Heiko Baums wrote:
Am Fri, 29 Apr 2011 11:02:22 +0200
schrieb Thomas Bächler:
Every recent operating system I know can handle UTC, even Windows
Vista (bugs before SP1, works with SP1 or later) and Windows 7, and
Windows XP is so old, it shouldn't be used anyway.
But the
Am Fri, 29 Apr 2011 10:04:30 +0800
schrieb Oon-Ee Ng :
> Isn't initscripts an Arch-specific project?
I don't know if those problems are just the initscripts or if localtime
shall just be ignored by the initscripts due to upstream issues. I even
don't know the issues.
Well, I don't care that much
Am Fri, 29 Apr 2011 11:02:22 +0200
schrieb Thomas Bächler :
> Every recent operating system I know can handle UTC, even Windows
> Vista (bugs before SP1, works with SP1 or later) and Windows 7, and
> Windows XP is so old, it shouldn't be used anyway.
But there's a problem with Windows. Updating W
Am Thu, 28 Apr 2011 22:22:39 -0500
schrieb C Anthony Risinger :
> a [brief] post-installation message seems a good compromise to me --
> maybe even the registry file itself too -- but in the absence of both
> this is still a good change imo.
This should not only be a brief post-installation messa
Am 29.04.2011 02:43, schrieb Heiko Baums:
> Am Fri, 29 Apr 2011 02:33:57 +0200
> schrieb Tom Gundersen :
>
>> * We now strongly discourage the use of HWCLOCK="localtime", as this
>> may lead to several known and unfixable bugs
>
> This can lead to problems on multi boot systems on which Arch
> Li
On Thu, Apr 28, 2011 at 9:10 PM, gt wrote:
> On Fri, Apr 29, 2011 at 03:19:04AM +0200, Heiko Baums wrote:
>> Am Fri, 29 Apr 2011 09:01:23 +0800
>> schrieb Oon-Ee Ng :
>>
>> > I was under the impression that windows versions from Windows XP
>> > onwards had a registry key which enabled them to use
On Fri, Apr 29, 2011 at 03:19:04AM +0200, Heiko Baums wrote:
> Am Fri, 29 Apr 2011 09:01:23 +0800
> schrieb Oon-Ee Ng :
>
> > I was under the impression that windows versions from Windows XP
> > onwards had a registry key which enabled them to use UTC time.
>
> Well, I'm not using Windows anymore
On Fri, Apr 29, 2011 at 9:52 AM, Heiko Baums wrote:
> Am Fri, 29 Apr 2011 09:38:51 +0800
> schrieb Oon-Ee Ng :
>
>> Conversely, perhaps we can assume that Windows users who are able to
>> install Arch Linux (and dual-boot, no less) are able to edit a
>> registry key =).
>>
>> I have two dual-boot
Am Fri, 29 Apr 2011 09:38:51 +0800
schrieb Oon-Ee Ng :
> Conversely, perhaps we can assume that Windows users who are able to
> install Arch Linux (and dual-boot, no less) are able to edit a
> registry key =).
>
> I have two dual-boot systems, I use UTC on one and localtime on the
> other, based
On Fri, Apr 29, 2011 at 9:19 AM, Heiko Baums wrote:
> Am Fri, 29 Apr 2011 09:01:23 +0800
> schrieb Oon-Ee Ng :
>
>> I was under the impression that windows versions from Windows XP
>> onwards had a registry key which enabled them to use UTC time.
>
> Well, I'm not using Windows anymore for many ye
Am Fri, 29 Apr 2011 09:01:23 +0800
schrieb Oon-Ee Ng :
> I was under the impression that windows versions from Windows XP
> onwards had a registry key which enabled them to use UTC time.
Well, I'm not using Windows anymore for many years. So I can be
wrong, but I didn't know such a registry key,
On Fri, Apr 29, 2011 at 8:43 AM, Heiko Baums wrote:
> Am Fri, 29 Apr 2011 02:33:57 +0200
> schrieb Tom Gundersen :
>
>> * We now strongly discourage the use of HWCLOCK="localtime", as this
>> may lead to several known and unfixable bugs
>
> This can lead to problems on multi boot systems on which
Am Fri, 29 Apr 2011 02:33:57 +0200
schrieb Tom Gundersen :
> * We now strongly discourage the use of HWCLOCK="localtime", as this
> may lead to several known and unfixable bugs
This can lead to problems on multi boot systems on which Arch
Linux is installed parallel to Windows. At least older Win
29 matches
Mail list logo
