From owner-freebsd-current Wed Feb 22 06:54:06 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id GAA14812 for current-outgoing; Wed, 22 Feb 1995 06:54:06 -0800 Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id GAA14804 for ; Wed, 22 Feb 1995 06:54:03 -0800 Received: (from dfr@localhost) by minnow.render.com (8.6.9/8.6.9) id OAA08853; Wed, 22 Feb 1995 14:55:27 GMT Date: Wed, 22 Feb 1995 14:55:24 +0000 (GMT) From: Doug Rabson To: David Greenman cc: current@FreeBSD.org Subject: Re: mountd changes In-Reply-To: <199502221404.GAA04430@corbin.Root.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk On Wed, 22 Feb 1995, David Greenman wrote: > >I have some changes here for mountd which do two things: > > > >(1) Stop it from moaning when more than one mountpoint in a given > >filesystem is exported. > > > >(2) Allow mounts of directories which have an exported initial > >segment. > > I thought (1) happens because of the screwy way that the system applies > protections - the first listed is the one that applies to the rest (i.e. only > one set of protections/options per filesystem). This is true. The problem is that vfs_export() returns EPERM when mountd attempts to export the mount point for a second time, and mountd does not add it to its exports list. As a workaround, I interpret EPERM as success. Probably bogus, I know but it was easier that changing vfs_export(). > I thought (2) was already supported via -alldirs ? Blimey. That'll teach me to RTFM before I start hacking :-) > > -DG > -- Doug Rabson, RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 71 251 4411 FAX: +44 71 251 0939