From owner-freebsd-current Tue Jan 26 07:51:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22135 for freebsd-current-outgoing; Tue, 26 Jan 1999 07:51:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA22129 for ; Tue, 26 Jan 1999 07:51:39 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id KAA25207; Tue, 26 Jan 1999 10:50:38 -0500 (EST) (envelope-from wollman) Date: Tue, 26 Jan 1999 10:50:38 -0500 (EST) From: Garrett Wollman Message-Id: <199901261550.KAA25207@khavrinen.lcs.mit.edu> To: Luigi Rizzo Cc: trost@cloud.rain.com (Bill Trost), current@FreeBSD.ORG Subject: Re: beginnings of a diskless boot sequence being committed In-Reply-To: <199901260643.HAA29514@labinfo.iet.unipi.it> References: <15510.917327374@grey.cloud.rain.com> <199901260643.HAA29514@labinfo.iet.unipi.it> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > the problem is that i don't know how well unionfs works, and i don't > have the ability to fix it. Please keep in mind that there are two *different* entiries being discussed here: 1) mount -o union 2) mount -t union (which should really be called `translucentfs'). The former is a generic property of the VFS layer; the latter is a specific filesystem with rather different properties. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message