Date: Wed, 23 Apr 2003 14:33:04 -0400 (EDT) From: John Baldwin <jhb@FreeBSD.org> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: freebsd-current@freebsd.org Subject: RE: module path? Message-ID: <XFMail.20030423143304.jhb@FreeBSD.org> In-Reply-To: <16038.56029.799743.49248@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.20030423143304.jhb>