Date: Thu, 11 Jan 2001 01:57:40 +0100 From: Cliff Sarginson <cliff@raggedclown.net> To: Greg Lehey <grog@lemis.com> Cc: j mckitrick <jcm@FreeBSD-uk.eu.org>, freebsd-questions@FreeBSD.ORG Subject: Re: changing CMOS time on a laptop Message-ID: <01011101574002.02338@buffy> In-Reply-To: <20010111105720.Q44170@wantadilla.lemis.com> References: <20010110193943.B38307@dogma.freebsd-uk.eu.org> <20010111004014.F970@buffy.raggedclown.net> <20010111105720.Q44170@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01011101574002.02338>