From: Adrian Bunk <bunk@stusta.de>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Setting the hardware clock together with the system one(was: Re: [patch 1/1] x86_64: make string func definition work as intended)
Date: Tue, 3 May 2005 00:00:30 +0200 [thread overview]
Message-ID: <20050502220030.GN3592@stusta.de> (raw)
In-Reply-To: <200505022136.42202.blaisorblade@yahoo.it>
On Mon, May 02, 2005 at 09:36:41PM +0200, Blaisorblade wrote:
> On Sunday 01 May 2005 17:53, Adrian Bunk wrote:
> > On Sun, May 01, 2005 at 09:08:51PM +0200, blaisorblade@yahoo.it wrote:
> > >... ^^^^^^^^^^^^^^^^
> >
> > Please correct the time settings on your computer.
> I'm doing it by hand at every reboot. Just discovered this stupid Gentoo
> default setting:
>
> # If you want to sync the system clock to the hardware clock during
> # shutdown, then say "yes" here.
>
> CLOCK_SYSTOHC="no"
>
> In other words, the kernel does not auto-adjusts the hardware clock? Well,
> that's not nice... (maybe only the Gentoo setting).
Besides such issues, it might also be an option to set the time using
NTP information at boot time or (if network is started later) when
starting your internet connection.
> Regards.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-05-02 22:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-01 19:08 [patch 1/1] x86_64: make string func definition work as intended blaisorblade
2005-05-02 16:41 ` Andi Kleen
[not found] ` <20050501155327.GX3592@stusta.de>
2005-05-02 19:36 ` Setting the hardware clock together with the system one(was: Re: [patch 1/1] x86_64: make string func definition work as intended) Blaisorblade
2005-05-02 22:00 ` Adrian Bunk [this message]
2005-05-03 7:21 ` [patch 1/1] x86_64: make string func definition work as intended Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050502220030.GN3592@stusta.de \
--to=bunk@stusta.de \
--cc=blaisorblade@yahoo.it \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox