On Wed, 25.01.12 14:49, David Thurgood (d.r.thurg...@gmx.com) wrote:
>Dear Sir,
>I am hoping that this is an appropriate place for a "feature request" with
>respect to the program hwclock.
>
>This relates to a very old problem, which as I remember goes back to the
>PC's of the
Hi David,
On Wed, Jan 25, 2012 at 3:49 PM, David Thurgood wrote:
> I am hoping that this is an appropriate place for a "feature request" with
> respect to the program hwclock.
hwclock is part of the util-linux package, so you'd probably have more
luck emailing . systemd does not write to
your rt
Dear Sir,
I am hoping that this is an appropriate place for a "feature
request" with respect to the program hwclock.
This relates to a very old problem, which as I remember goes back
to the PC's of the 70's and 80's. My present PC seems to have
just
On Mon, Jan 24, 2011 at 22:31, Lennart Poettering
wrote:
> I think using env vars for timezone configuration is not a good idea,
> and if used should be used exclusively to override system configuration
> per-user. I don't think it should be used on the system level and the
> hwclock logic we hav
On Sun, 23.01.11 00:01, Tom Gundersen (t...@jklm.no) wrote:
>
> Hi guys,
>
> Further to my previous mail about hwclock, I'm struggling to get my
> head around what is the "proper" way to handle hwclock's adjfile.
>
> These are my assumptions:
>
> /etc is in principle mounted read-only (not yet
On Sat, 22.01.11 21:44, Tom Gundersen (t...@jklm.no) wrote:
> Hi guys,
>
> I'm trying to figure out how our hwclock handling works, and in
> particular if there are any scenarios we don't handle.
>
> First, I think there is a typo in the explanation given in
> hwclock-load.service. Is the attach
On Sun, Jan 23, 2011 at 00:01, Tom Gundersen wrote:
> Further to my previous mail about hwclock, I'm struggling to get my
> head around what is the "proper" way to handle hwclock's adjfile.
>
> These are my assumptions:
>
> /etc is in principle mounted read-only (not yet possible, but that's
> the
On Sat, Jan 22, 2011 at 21:44, Tom Gundersen wrote:
> I'm trying to figure out how our hwclock handling works, and in
> particular if there are any scenarios we don't handle.
>
> First, I think there is a typo in the explanation given in
> hwclock-load.service. Is the attached patch correct?
>
> S
Hi guys,
Further to my previous mail about hwclock, I'm struggling to get my
head around what is the "proper" way to handle hwclock's adjfile.
These are my assumptions:
/etc is in principle mounted read-only (not yet possible, but that's
the goal, right?)
/var is in principle not available durin
Hi guys,
I'm trying to figure out how our hwclock handling works, and in
particular if there are any scenarios we don't handle.
First, I think there is a typo in the explanation given in
hwclock-load.service. Is the attached patch correct?
Secondly, hwclock allows us to specify whether the hardw
10 matches
Mail list logo
