From owner-freebsd-current Mon Jan 25 21:13:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA02229 for freebsd-current-outgoing; Mon, 25 Jan 1999 21:13:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from jli.com (jli.com [199.2.111.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA02223 for ; Mon, 25 Jan 1999 21:12:59 -0800 (PST) (envelope-from trost@cloud.rain.com) Received: (qmail 23264 invoked by uid 4); 26 Jan 1999 05:12:58 -0000 Received: (qmail 15513 invoked from network); 26 Jan 1999 05:09:35 -0000 Received: from localhost.cloud.rain.com (HELO grey.cloud.rain.com) (127.0.0.1) by localhost.cloud.rain.com with SMTP; 26 Jan 1999 05:09:35 -0000 To: current@FreeBSD.ORG Subject: Re: beginnings of a diskless boot sequence being committed References: <199901251604.RAA27194@labinfo.iet.unipi.it> In-reply-to: Your message of Mon, 25 Jan 1999 17:04:14 +0100. <199901251604.RAA27194@labinfo.iet.unipi.it> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <15509.917327374.1@grey.cloud.rain.com> Date: Mon, 25 Jan 1999 21:09:34 -0800 Message-ID: <15510.917327374@grey.cloud.rain.com> From: Bill Trost Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luigi Rizzo writes: > :I haven't seen how you suggest to build&populate the MFS filesystems -- ... > There isn't much to build. Most of the MFS filesystems start > out empty. ok here we use a different approach. For simplicity I am using a single MFS system with all the things you put in /var, and including /var/dev and /var/etc (with /dev -> /var/dev and /etc -> /var/etc on the diskless machine). I have a wacky idea in this vein that I want to pursue sometime -- instead of pushing off lots of symlinks for the various writable portions of the read-only root directory (which strikes as a bit odd in itself), I was considering union-mounting an MFS filesystem directly over the read-only root partition. The advantage of this approach is that you do not have to know ahead of time what portions of the read-only partition need to be writable -- files get copied into the MFS partition only if and when they are written to. Thoughts? It seems like it would be feasible, and it might even be possible to do it directly in /etc/fstab without having to put any sort of cleverness in /etc/rc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message