From owner-freebsd-stable@FreeBSD.ORG Fri May 28 19:26:12 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 6DAE61065677 for ; Fri, 28 May 2010 19:26:12 +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 4EACF8FC18 for ; Fri, 28 May 2010 19:26:12 +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 o4SJQCW3041849; Fri, 28 May 2010 12:26:12 -0700 (PDT) Message-Id: <201005281926.o4SJQCW3041849@hugeraid.jetcafe.org> X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.0.4 To: Jeremy Chadwick In-reply-to: <20100528191828.GA83371@icarus.home.lan> References: <201005272348.o4RNmgWh014243@hugeraid.jetcafe.org> <20100528043006.GA18560@lava.net> <201005281757.o4SHvTwq020905@hugeraid.jetcafe.org> <20100528191828.GA83371@icarus.home.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 May 2010 12:26:12 -0700 From: Dave Hayes Cc: freebsd-stable@freebsd.org, Clifton Royston 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: Fri, 28 May 2010 19:26:12 -0000 Jeremy Chadwick writes: > On Fri, May 28, 2010 at 10:57:29AM -0700, Dave Hayes wrote: >> Clifton Royston writes: >> > It sounds like what you really want is to load the contents of the >> > specified file as a memory system? That's not part of mdconfig's >> > repertoire, to the best of my recollection. >> >> So if, in /etc/loader.conf, I do this: >> >> rootfs_load="YES" >> rootfs_type="mfs_root" >> rootfs_name="/mfsboot" >> vfs.root.mountfrom="ufs:md0" > > I think you mean /boot/loader.conf? Yes, you are correct. > And I think you meant this for variable names, in addition to what > vfs.root.mountfrom should be (specific to RELENG_8): > mfsroot_load="YES" > mfsroot_type="mfs_root" > mfsroot_name="/some/path/mfsroot" I'm using RELENG_7, but it seems rootfs_* works just like mfsroot_* ... is the former deprecated? > vfs.root.mountfrom="ufs:/dev/md0" Hm, 'ufs:md0' currently works. What trouble can be had from using the abbreviated device name? > If using RELENG_7 and the mfsroot was made on RELENG_7, replace > "/dev/md0" with "/dev/md0c". Is there a reason for doing this? -- Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org >>> The opinions expressed above are entirely my own <<< If you want to strengthen an enemy -- hate them.