From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org)
by finch.gentoo.org with esmtp (Exim 4.60)
(envelope-from <gentoo-amd64+bounces-9942-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1KfjSG-0001lg-MK
for garchives@archives.gentoo.org; Tue, 16 Sep 2008 22:55:32 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id D2C92E07C2;
Tue, 16 Sep 2008 22:55:31 +0000 (UTC)
Received: from ciao.gmane.org (main.gmane.org [80.91.229.2])
by pigeon.gentoo.org (Postfix) with ESMTP id A5060E07C2
for <gentoo-amd64@lists.gentoo.org>; Tue, 16 Sep 2008 22:55:31 +0000 (UTC)
Received: from list by ciao.gmane.org with local (Exim 4.43)
id 1KfjSD-0008Uv-2B
for gentoo-amd64@lists.gentoo.org; Tue, 16 Sep 2008 22:55:29 +0000
Received: from ip68-231-12-43.ph.ph.cox.net ([68.231.12.43])
by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
id 1AlnuQ-0007hv-00
for <gentoo-amd64@lists.gentoo.org>; Tue, 16 Sep 2008 22:55:29 +0000
Received: from 1i5t5.duncan by ip68-231-12-43.ph.ph.cox.net with local (Gmexim 0.1 (Debian))
id 1AlnuQ-0007hv-00
for <gentoo-amd64@lists.gentoo.org>; Tue, 16 Sep 2008 22:55:29 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: gentoo-amd64@lists.gentoo.org
From: Duncan <1i5t5.duncan@cox.net>
Subject: [gentoo-amd64] Re: hardware clock often doesn't sync to system on shutdown
Date: Tue, 16 Sep 2008 22:55:21 +0000 (UTC)
Message-ID: <pan.2008.09.16.22.55.21@cox.net>
References: <48CA0929.60003@asyr.hopto.org>
<pan.2008.09.14.08.44.00@cox.net> <48CD973B.6080308@asyr.hopto.org>
<pan.2008.09.15.08.49.27@cox.net> <48CE7530.2090909@asyr.hopto.org>
<48CE77C9.7090605@getdesigned.at> <48CE7EAE.9080404@asyr.hopto.org>
<pan.2008.09.15.22.31.47@cox.net> <48CFB464.8030008@asyr.hopto.org>
Precedence: bulk
List-Post: <mailto:gentoo-amd64@lists.gentoo.org>
List-Help: <mailto:gentoo-amd64+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-amd64+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-amd64+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-amd64.gentoo.org>
X-BeenThere: gentoo-amd64@lists.gentoo.org
Reply-to: gentoo-amd64@lists.gentoo.org
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: ip68-231-12-43.ph.ph.cox.net
User-Agent: Pan/0.133 (House of Butterflies)
Sender: news <news@ger.gmane.org>
Content-Transfer-Encoding: quoted-printable
X-Archives-Salt: 44609ac6-5b5e-413f-8930-129b57d84595
X-Archives-Hash: 1d91c8d723985521777f7158ea28bcf7
Thanasis <thanasis@asyr.hopto.org> posted 48CFB464.8030008@asyr.hopto.org=
,
excerpted below, on Tue, 16 Sep 2008 16:28:04 +0300:
> Do you think it might cause any problems, to /dev/null maybe?
I'm not sure how it's handled in this case, but the ones that cause=20
problems redirecting to /dev/null are I believe the ones that rewrite by=20
writing a temp version, then mv-ing it over the old one. In fact, some=20
of those won't work with symlinks for much the same reason.
Of course, if it's trying to do that as a normal user, it won't work, but=
=20
if it's doing that as root (as likely here) it can cause problems. I've=20
had it happen a couple times to me...
So I'd try starting and stopping clock a time or two and then check /dev/
null to see if it's still fine. But make sure you either have a copy of=20
the device node or know how to create one, before you do. If you're=20
using udev, you should have a copy of both the null and console device=20
nodes either in the /dev on / before udev mounts over it (so you can=20
access it by doing a mount --bind... I have an fstab entry for just that,=
=20
to make doing backups of the / filesystem easier), or in your initramfs/
initrd, or both.
--=20
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman