From owner-freebsd-current@FreeBSD.ORG Mon Jun 16 20:10:47 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4B39137B401 for ; Mon, 16 Jun 2003 20:10:47 -0700 (PDT) Received: from helios.earthmagic.org (helios.earthmagic.org [198.78.66.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id B6F3243F93 for ; Mon, 16 Jun 2003 20:10:46 -0700 (PDT) (envelope-from lonewolf-freebsd@earthmagic.org) Received: (qmail 21579 invoked from network); 17 Jun 2003 03:10:45 -0000 Received: from ppp1096.vic.padsl.internode.on.net (HELO earthmagic.org) (lonewolf@150.101.221.71) by helios.earthmagic.org with RC4-MD5 encrypted SMTP; 17 Jun 2003 03:10:45 -0000 Message-ID: <3EEE8780.4050804@earthmagic.org> Date: Tue, 17 Jun 2003 13:14:08 +1000 From: Johny Mattsson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030524 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <3EEE7A15.6070904@earthmagic.org> <20030617022842.KIUS27254.pop017.verizon.net@kokeb.ambesa.net> In-Reply-To: <20030617022842.KIUS27254.pop017.verizon.net@kokeb.ambesa.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: 5.1-R: rcNG - 'mountall' missing? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2003 03:10:47 -0000 Mike Makonnen wrote: > This stems from the fact that the way we handle filesystems is different from > the way NetBSD handles it. For our purposes, we need one pass to mount local > filesystems and a second one to mount remote ones. Ah, okay. I haven't actually been root on a NetBSD box, so I'm not too familiar with that side of the fence I'm afraid. Now, to (maybe) throw a spanner in the works, I'm currently working on a couple of scripts to allow the handling of md(4) based filesystems at boot time. Personally I have a need for vnode type file systems, but I'm making it so that malloc/swap filesystems are also handled (e.g. for /tmp). The issue that arises from this support is that I can't safely have the md devices attach before all the file systems are mounted since I don't know on which fs any vnode backing files reside on (and I don't want to have to do a two-pass; one for malloc/swap and one for vnode). It could potentially be a case where you want/need to attach to a file that's on a remote system (via nfs or even smb perhaps). From my scripts' point of view this isn't too bad, as I can just depend on 'mountall' (or so I think at least), but in doing so I'm perverting the meaning of 'mountall', as not all filesystems will be mounted by then. I'm not sure what the best approach would be, so I'd like some feedback on this. Would it be acceptable to introduce another dummy target (like FILESYSTEMS)? From a purely FreeBSD perspective I would probably find this the cleanest, but I know we need to play nice with NetBSD too (do they have anything like md or vn?) so that might stuff things up. I'm really open to suggestions here, and if there isn't any interest in getting md boot-time support into the baseline I'm happy to keep it as a set of local patches, but I suspected that if I write it in such a way that a swap backed /tmp is possible to achieve with a simple rc.conf tweak and a supporting file, then that might be something a number of people would be interested in. I'll post a patch set in a day or two when I've tuned the scripts a bit more (hopefully in response to feedback). > IIRC NetBSD requires that users specify their file systems in rc.conf. This > might be useful to have on FreeBSD, as long as it's strictly optional, but I > don't have the time or interest to work on it. Interesting, but nothing I'd find useful either at the moment, so I'll pass on that task :) Cheers, /Johny