From owner-freebsd-current@FreeBSD.ORG Wed Apr 23 11:33:05 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA53437B401 for ; Wed, 23 Apr 2003 11:33:05 -0700 (PDT) Received: from mail.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2DF1243F85 for ; Wed, 23 Apr 2003 11:33:05 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 22510 invoked from network); 23 Apr 2003 18:33:10 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 23 Apr 2003 18:33:10 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.8/8.12.8) with ESMTP id h3NIX0Ov097050; Wed, 23 Apr 2003 14:33:01 -0400 (EDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <16038.56029.799743.49248@grasshopper.cs.duke.edu> Date: Wed, 23 Apr 2003 14:33:04 -0400 (EDT) From: John Baldwin To: Andrew Gallatin cc: freebsd-current@freebsd.org Subject: RE: module path? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Apr 2003 18:33:06 -0000 On 23-Apr-2003 Andrew Gallatin wrote: > > What's the official way to boot an alternate kernel these days? > > I upgraded the kernel sources and installed the resulting kernel and > *.ko in /boot/kernel.test/ > > I then booted, broke into the loader, and told it to load > /boot/kernel.test/kernel. When doing this, I expected that the module > path would get set so that /boot/kernel.test was first. Nope. > It auto-loaded /boot/kernel/acpi.ko. Then there was an > earth-shattering kaboom :-( > > Is there a way to boot an alternate kernel which sets the module path > for you? I usually do: OK boot kernel.test except I call them all /boot/smpng/kernel, /boot/proc/kernel and do OK boot smpng or OK boot proc -s -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/