From owner-freebsd-questions  Wed Jan 10 17: 4:42 2001
Delivered-To: freebsd-questions@freebsd.org
Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20])
	by hub.freebsd.org (Postfix) with ESMTP id B0C8A37B400
	for <freebsd-questions@freebsd.org>; Wed, 10 Jan 2001 17:04:24 -0800 (PST)
Received: from [212.238.77.116] (helo=willow.raggedclown.net)
	by post.mail.nl.demon.net with smtp (Exim 3.14 #2)
	id 14GWAA-0002OA-00; Thu, 11 Jan 2001 01:04:23 +0000
Received: from buffy.raggedclown.net (btvs.demon.nl [192.168.1.2])
	by willow.raggedclown.net (Postfix) with ESMTP
	id 6B9225DA1; Thu, 11 Jan 2001 02:03:46 +0100 (CET)
Received: by buffy.raggedclown.net (Postfix on SuSE Linux 7.0 (i386), from userid 500)
	id 55DA412C15; Thu, 11 Jan 2001 01:57:42 +0100 (CET)
From: Cliff Sarginson <cliff@raggedclown.net>
Date: Thu, 11 Jan 2001 01:57:40 +0100
X-Mailer: KMail [version 1.1.99]
Content-Type: text/plain;
  charset="us-ascii"
Cc: j mckitrick <jcm@FreeBSD-uk.eu.org>,
	freebsd-questions@FreeBSD.ORG
To: Greg Lehey <grog@lemis.com>
References: <20010110193943.B38307@dogma.freebsd-uk.eu.org> <20010111004014.F970@buffy.raggedclown.net> <20010111105720.Q44170@wantadilla.lemis.com>
In-Reply-To: <20010111105720.Q44170@wantadilla.lemis.com>
Subject: Re: changing CMOS time on a laptop
MIME-Version: 1.0
Message-Id: <01011101574002.02338@buffy>
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thursday 11 January 2001 01:27, Greg Lehey wrote:
> On Thursday, 11 January 2001 at  0:40:14 +0100, Cliff Sarginson wrote:
> > On Wed, Jan 10, 2001 at 07:39:43PM +0000, j mckitrick wrote:
> >> OK, I know 'date' can be used to change the *kernel* time, but the
> >> CMOS clock is still holding the old time.  What do I use to change
> >> it?
> >
> > hwclock --utc --systohc
>
> Have you tried this?
>
>   # hwclock --utc --systohc
>   hwclock: not found
>
> hwclock is a kludge used in Linux to make up for the fact that the
> date(1) command doesn't set the CMOS clock correctly.  
Well, it is actually a bit more complicated than that on Linux..
but that is another story..

FreeBSD's
> implementation of date(1) *does* set the CMOS clock correctly, so
> there's no hwclock.
>
> This doesn't help Jonathon, of course.  Without knowing more about
> his laptop, it's difficult to answer that question.  Most laptops set
> time with no problems.
>
Sorry sorry .. I did try it, but on the wrong computer ..

Cliff


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message