From owner-freebsd-mobile  Sun Jun 13 20:18:21 1999
Delivered-To: freebsd-mobile@freebsd.org
Received: from lab12.ie.pitt.edu (lab12.ie.pitt.edu [136.142.89.102])
	by hub.freebsd.org (Postfix) with ESMTP id 4E14114CA0
	for <freebsd-mobile@freebsd.org>; Sun, 13 Jun 1999 20:18:19 -0700 (PDT)
	(envelope-from grafe@lab12.ie.pitt.edu)
Received: (from grafe@localhost)
	by lab12.ie.pitt.edu (8.8.8+Sun/8.8.8) id XAA23491
	for freebsd-mobile@freebsd.org; Sun, 13 Jun 1999 23:18:18 -0400 (EDT)
Date: Sun, 13 Jun 1999 23:18:18 -0400 (EDT)
Message-Id: <199906140318.XAA23491@lab12.ie.pitt.edu>
From: grafe@lab12.ie.pitt.edu (Gary Rafe)
To: freebsd-mobile@freebsd.org
Subject: Q: How to get "uptime" to report calendar time since boot...
Sender: owner-freebsd-mobile@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

I very recently upgraded my Toshiba 330CDS from 2.2.8R to 3.2R
and am quite happy with the results.

I noted that the pcic driver wasn't catching insert/remove events of my
3Com Etherlink card, so I pulled in the new PAO3 release,
and that works fine, as does suspend/resume and power-down.

I'm now curious as to how to configure the kernel so that "uptime"
reports "calendar" time since last boot, rather than actual "up" time
(i.e., time slept not recorded).
The current behavior differs from 2.2.x.

Thanks.

Gary Rafe
gerst4+@pitt.edu


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