Date: Thu, 11 Jan 2007 00:25:44 +0100 From: Torfinn Ingolfsen <torfinn.ingolfsen@broadpark.no> To: freebsd-stable@freebsd.org Subject: Re: booting question Message-ID: <20070111002544.9cfc6e14.torfinn.ingolfsen@broadpark.no> In-Reply-To: <20070110202600.4C20D45041@ptavv.es.net> References: <184b087c0701101154x4bf948e7k8f00d4f9e7e2a8d6@mail.gmail.com> <20070110202600.4C20D45041@ptavv.es.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 10 Jan 2007 12:26:00 -0800 Kevin Oberman <oberman@es.net> wrote: > This may or may not work depending on modules loaded (note that unload > will unload all modules already loaded by the loader, not just the > kernel) and whether any modules are loaded later in the boot > process. While I have not check in quite a while, at one time this > would result in modules still being loaded from /boot/kernel and > these might not be compatible with the old kernel. FWIW, I had to boot a machine with the install CD (6.2-RC2, cd1) the other day, because FreeBSD's boot manager was hosed, erm, overwritten by Linux (which I had installed on another partition. Not my fault that the Linux installation program didn't ask me hwere to put grub, oh well) What I wanted was to use boot0cfg to write FreeBSD's boot manager back onto the MBR, but since I didn't have a rescue CD, I had to boot the machine with CD1, and then make it get everything from the hard drive and boot from there. I knew that may FreeBSD installation was on disk0, slice 1. What I did was the following (IIRC): 1) boot from CD1 2) select command line from boot menu 3) unload 4) set currdev=disk0s1 5) load kernel 6) boot (actually, I think I used boot -a, but I don't know if that is necessary) HTH -- Regards, Torfinn Ingolfsen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070111002544.9cfc6e14.torfinn.ingolfsen>