From owner-cvs-src@FreeBSD.ORG Sat Apr 9 14:02:28 2005 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 38BEA16A4CE; Sat, 9 Apr 2005 14:02:28 +0000 (GMT) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CE3C43D2F; Sat, 9 Apr 2005 14:02:28 +0000 (GMT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 04B8D5CA3A; Sat, 9 Apr 2005 07:02:28 -0700 (PDT) Date: Sat, 9 Apr 2005 07:02:27 -0700 From: Alfred Perlstein To: Jeff Roberson Message-ID: <20050409140227.GO60345@elvis.mu.org> References: <200504091204.j39C4aH4033816@repoman.freebsd.org> <20050409125239.GI60345@elvis.mu.org> <20050409085414.M28571@mail.chesapeake.net> <20050409132339.GJ60345@elvis.mu.org> <20050409093326.C28571@mail.chesapeake.net> <20050409134626.GL60345@elvis.mu.org> <20050409135322.GM60345@elvis.mu.org> <20050409095543.N28571@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050409095543.N28571@mail.chesapeake.net> User-Agent: Mutt/1.4.2.1i cc: cvs-src@FreeBSD.org cc: Jeff Roberson cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/sys namei.h src/sys/kern vfs_syscalls.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Apr 2005 14:02:28 -0000 * Jeff Roberson [050409 06:56] wrote: > On Sat, 9 Apr 2005, Alfred Perlstein wrote: > > > * Alfred Perlstein [050409 06:46] wrote: > > > * Jeff Roberson [050409 06:33] wrote: > > > > > > > > I don't understand, where does autofs inspect this flag? > > > > You are right about the name being misleading and the docs being > > nearly useless to explain it. I will update the docs to reflect > > what it actually is useful for when we get this fixed up. > > Where is the actual code that inspects this, is what I'm asking. I > understand the use-case, I just don't know where that actually happens. It is not currently published, but doing this puts yet another hurdle in the way of me publishing it. And as Jim Reese said, nfsv4 can make use of it. -- - Alfred Perlstein - Research Engineering Development Inc. - email: bright@mu.org cell: 408-480-4684