From owner-freebsd-arch Wed Oct 25 10: 6:18 2000 Delivered-To: freebsd-arch@freebsd.org Received: from mail-relay.eunet.no (mail-relay.eunet.no [193.71.71.242]) by hub.freebsd.org (Postfix) with ESMTP id F31FA37B4C5 for ; Wed, 25 Oct 2000 10:06:15 -0700 (PDT) Received: from login-1.eunet.no (login-1.eunet.no [193.75.110.2]) by mail-relay.eunet.no (8.9.3/8.9.3/GN) with ESMTP id TAA26213; Wed, 25 Oct 2000 19:06:14 +0200 (CEST) (envelope-from mbendiks@eunet.no) Received: from localhost (mbendiks@localhost) by login-1.eunet.no (8.9.3/8.8.8) with ESMTP id TAA54788; Wed, 25 Oct 2000 19:06:14 +0200 (CEST) (envelope-from mbendiks@eunet.no) X-Authentication-Warning: login-1.eunet.no: mbendiks owned process doing -bs Date: Wed, 25 Oct 2000 19:06:14 +0200 (CEST) From: Marius Bendiksen To: Keith Stevenson Cc: arch@FreeBSD.ORG Subject: Re: Ideas concerning fsck In-Reply-To: <20001024090152.A10742@osaka.louisville.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is there documentation somewhere on how to do this? I've looked at the > memory based filesystem stuff before, but was unable to figure out what steps > needed to be performed in order to boot from it. If you have a look at the release build process, you'll see that you basically need to newfs a vn device, stick the appropriate files on it, and have "load -t md_image /my-mfs-image" in your loader script. If you fail to bring along /etc/fstab, you will need to pass some flags to the kernel to let it know whence the root fs comes from, IIRC. Marius To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message