From owner-freebsd-current Fri Oct 27 21:56:40 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA12700 for current-outgoing; Fri, 27 Oct 1995 21:56:40 -0700 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA12679 for ; Fri, 27 Oct 1995 21:56:36 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id VAA27327; Fri, 27 Oct 1995 21:47:16 -0700 From: Terry Lambert Message-Id: <199510280447.VAA27327@phaeton.artisoft.com> Subject: Re: fs layering pathces doesn't work. To: terry@lambert.org (Terry Lambert) Date: Fri, 27 Oct 1995 21:47:16 -0700 (MST) Cc: phk@critter.tfs.com, terry@lambert.org, phk@freefall.freebsd.org, current@freebsd.org In-Reply-To: <199510241911.MAA13911@phaeton.artisoft.com> from "Terry Lambert" at Oct 24, 95 12:11:48 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 875 Sender: owner-current@freebsd.org Precedence: bulk There, dammit. Man, it is impossible to do diffs against -current! The latest full patches which work are now in: freefall.cdrom.com:~terry/fs_layer_patch.gz These should fix all the problems in the ancillary file systems and in the mkdir and link calls (your panic was in mkdir). Turns out that some hunks failed in the patching because of the ROFS changes (which I don't have time to look at right now, so we'll assume they were fixed corectly by swapping VOP vectors or that the underlying file system won't puke). Because they failed locally, they didn't get rolled into the patch set. I guess this is the problem with patches that touch lots of files. Thank *god* I won't need to do something like this again for a while. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.