From owner-freebsd-stable@FreeBSD.ORG Mon May 31 02:42:48 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 77E241065670 for ; Mon, 31 May 2010 02:42:48 +0000 (UTC) (envelope-from dave@jetcafe.org) Received: from hugeraid.jetcafe.org (hugeraid.jetcafe.org [205.147.26.109]) by mx1.freebsd.org (Postfix) with ESMTP id 546898FC12 for ; Mon, 31 May 2010 02:42:47 +0000 (UTC) Received: from hugeraid.jetcafe.org (localhost [127.0.0.1]) by hugeraid.jetcafe.org (8.13.8/8.13.8) with ESMTP id o4V2glZX057087; Sun, 30 May 2010 19:42:47 -0700 (PDT) Message-Id: <201005310242.o4V2glZX057087@hugeraid.jetcafe.org> X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.0.4 To: Garrett Cooper In-reply-to: References: <201005272348.o4RNmgWh014243@hugeraid.jetcafe.org> <20100528043006.GA18560@lava.net> <201005281757.o4SHvTwq020905@hugeraid.jetcafe.org> <20100528191828.GA83371@icarus.home.lan> <201005281926.o4SJQCW3041849@hugeraid.jetcafe.org> <20100528215837.GA86689@icarus.home.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 30 May 2010 19:42:47 -0700 From: Dave Hayes Cc: freebsd-stable@freebsd.org, Clifton Royston , Jeremy Chadwick Subject: Re: Locking a file backed mdconfig into memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 May 2010 02:42:48 -0000 Garrett Cooper writes: > This is how I do it in my quickie loader.rc: > include /boot/loader.4th > set vfs.root.mountfrom="ufs:/dev/md0" > load /kernel > load -t mfs_root /mfsroot > start I used to do exactly this back at FreeBSD 4.11 to boot off a cdrom. Nice to know it still works this way. Jeremy Chadwick writes: > However, what I'm having trouble understanding is what exactly > preload_search_info() looks for and how all this actually connects > and works. It appears to me that there are specific drivers located in > src/sys/dev that are KLD-supported and others which are expected to be > included in the kernel statically. Maybe this confusion explains why /dev/md0c is giving me random crashes at the moment? Of course, another theory might be the size of my initial ramdisk (300Mb). Would there any known bug where booting off a large ramdisk causes unreadable panics to flash past the console too rapidly to view? -- Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org >>> The opinions expressed above are entirely my own <<< By and large, language is a tool for concealing the truth. -George Carlin