From owner-freebsd-questions@FreeBSD.ORG Thu Dec 25 16:17:34 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 81747106567A for ; Thu, 25 Dec 2008 16:17:34 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (brucec-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:c09::2]) by mx1.freebsd.org (Postfix) with ESMTP id 418DE8FC1B for ; Thu, 25 Dec 2008 16:17:34 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id D13C9192D0; Thu, 25 Dec 2008 11:17:32 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on muon X-Spam-Level: X-Spam-Status: No, score=-1.2 required=8.0 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.2.5 Received: from gluon (unknown [IPv6:2a01:348:10f:0:240:f4ff:fe57:9871]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA; Thu, 25 Dec 2008 11:17:32 -0500 (EST) Date: Thu, 25 Dec 2008 16:17:26 +0000 From: Bruce Cran To: "Jason C. Wells" Message-ID: <20081225161726.052b5ee3@gluon> In-Reply-To: <4953A926.7030700@highperformance.net> References: <4953A926.7030700@highperformance.net> X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.9; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd general questions Subject: Re: Persistent Kernel Variables X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Dec 2008 16:17:34 -0000 On Thu, 25 Dec 2008 07:39:18 -0800 "Jason C. Wells" wrote: > I have a new kernel variable in /boot/device.hints. > > kern.timecounter.hardware="i8254" > > but it's not set during boot. I have other hints that are set > during boot. Why is kern.timecounter.hardware not being set? How > can I fix it. I think it's something that has to be set later during boot, via /etc/sysctl.conf. I tried setting it through /boot/loader.conf and it didn't work but there's no problem setting it once the system has booted. -- Bruce Cran