From owner-freebsd-questions Fri Oct 27 16: 7: 1 2000 Delivered-To: freebsd-questions@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id C50E537B479 for ; Fri, 27 Oct 2000 16:06:58 -0700 (PDT) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (8.10.1/8.10.1) with ESMTP id e9RN6U128726; Fri, 27 Oct 2000 16:06:30 -0700 (PDT) Message-Id: <200010272306.e9RN6U128726@ptavv.es.net> To: "Bennett Hui" Cc: "Mike Galvez" , "Bennett Hui" , smujohnson@home.com, questions@FreeBSD.ORG Subject: Re: APM or /etc/hosts In-reply-to: Your message of "Fri, 27 Oct 2000 01:03:39 PDT." Date: Fri, 27 Oct 2000 16:06:30 -0700 From: "Kevin Oberman" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I believe that /boot/kernel.conf is normally created when you use the configuration screen that comes up when you boot off of the installation media. I can easily build an installation medium that skips this (not recommended) and does not create the file. But selecting the option that reads something like "I know what I'm doing, so let's just get on with it" also skips it. I suspect that this is the reason you lack it. That said, you can always create the file and add: en apm q into it. (Not sure what happens when you leave off the trailing 'q'.) The other easy fix is to delete the word "disable" from the "device apm0" line in the configuration file. This keyword causes the device to be built into the kernel, but it is not enabled at boot time. The kernel.conf overrides this. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message