From owner-freebsd-current Tue Jan 26 03:03:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA15944 for freebsd-current-outgoing; Tue, 26 Jan 1999 03:03:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA15923 for ; Tue, 26 Jan 1999 03:02:53 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id HAA29514; Tue, 26 Jan 1999 07:43:42 +0100 From: Luigi Rizzo Message-Id: <199901260643.HAA29514@labinfo.iet.unipi.it> Subject: Re: beginnings of a diskless boot sequence being committed To: trost@cloud.rain.com (Bill Trost) Date: Tue, 26 Jan 1999 07:43:42 +0100 (MET) Cc: current@FreeBSD.ORG In-Reply-To: <15510.917327374@grey.cloud.rain.com> from "Bill Trost" at Jan 25, 99 09:09:15 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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 the problem is that i don't know how well unionfs works, and i don't have the ability to fix it. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message