Date: Tue, 15 May 2007 11:05:41 +0200 From: des@des.no (Dag-Erling =?utf-8?Q?Sm=C3=B8rgrav?=) To: "Matthew D. Fuller" <fullermd@over-yonder.net> Cc: freebsd-hackers@freebsd.org, David Cramblett <david@functionalchaos.net> Subject: Re: System Drops to manual mount root prompt after HDD duplication Message-ID: <861whiihi2.fsf@dwp.des.no> In-Reply-To: <20070515064408.GK78897@over-yonder.net> (Matthew D. Fuller's message of "Tue\, 15 May 2007 01\:44\:08 -0500") References: <4640EAD0.3020502@mesd.k12.or.us> <4647D88D.5060404@functionalchaos.net> <86wszbx3tu.fsf@dwp.des.no> <4648835D.9020306@functionalchaos.net> <86sl9ywque.fsf@dwp.des.no> <20070515064408.GK78897@over-yonder.net>
next in thread | previous in thread | raw e-mail | index | archive | help
"Matthew D. Fuller" <fullermd@over-yonder.net> writes: > Dag-Erling Sm=C3=B8rgrav <des@des.no> writes: > > Beats me... I can't even remember what userconfig_script is > > supposed to do. Note that support for 5.2.1 ended on July 31, 2004. > Neither can I, but last weekend I upgraded some 4.x boxes to 5.x and > then 6.x, and with the 5.x loader they croaked before booting until I > took those userconfig_script_load lines out. Ooh, now I remember; userconfig was the old hardware configuration mechanism we had before device.hints. If you typed -c at the boot1 prompt, you would get an interactive display where you could assign IRQs and ports to devices. The script is basically a sequence of userconfig commands; you could extract it from kenv after an interactive boot and store it in a file which the loader would read the next time around. AFAIR, userconfig was axed between FreeBSD 3 and 4, so there would be no point in loading a userconfig script for a 5.x kernel. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?861whiihi2.fsf>