From owner-freebsd-current Fri Feb 26 21:17: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id A83DB15089 for ; Fri, 26 Feb 1999 21:17:02 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id VAA08150; Fri, 26 Feb 1999 21:16:45 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id VAA05738; Fri, 26 Feb 1999 21:16:41 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 26 Feb 1999 21:16:41 -0800 (PST) Message-Id: <199902270516.VAA05738@vashon.polstra.com> To: dot@dotat.at Subject: Re: mount -o union broken recently? In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Tony Finch wrote: > Luigi Rizzo wrote: > > > >i just experienced the above today while trying diskless, and while > >ls only seems to return the entries for the topmost directory, files > >are accessible if you know the name. no idea if this is of any help. > > This is exactly the right pointer, thanks! The problem appears to be > the change between revs 1.108 and 1.109 of sys/kern/vfs_syscalls.c. A > couple of (very similar) blocks of code related to `mount -o union` > seem to have been mixed up with some code related to `mount -t union` > and therefore removed. It's a shame that the two things get confused > so much. I originally missed vfs_syscalls.c because a `find > /usr/src/sys | xargs grep MNT_UNION` on 3.1 didn't show it. Replacing > the errant code fixes the problem. Here's a patch against 1.112.2.1. Great sleuthing, guys! John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message