From owner-freebsd-current@FreeBSD.ORG Wed Jun 2 08:47:48 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1060) id BFF3F1065673; Wed, 2 Jun 2010 08:47:48 +0000 (UTC) Date: Wed, 2 Jun 2010 01:47:48 -0700 From: Craig Rodrigues To: John Baldwin Message-ID: <20100602084748.GA68872@crodrigues.org> References: <9EA890DC-CDCF-4E12-BB0E-063153400AB6@samsco.org> <201006011125.00062.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201006011125.00062.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org, Ivan Voras Subject: Re: SUJ and "mount" reporting X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2010 08:47:48 -0000 On Tue, Jun 01, 2010 at 11:25:00AM -0400, John Baldwin wrote: > My understanding of nmount() is that that is what it does now. However, not > everything is fully updated for nmount(). struct nfsargs is still passed in > as a blob value with the key "nfsargs" for example. This is not true any more. Doug Rabson and I modified src/usr.sbin/mount_nfs so that it passes individual string options via nmount() down to the kernel, which then parses the string options. Doug added a fallback_mount() function which reverts to the old behavior of passing a blob with key "nfsargs" for older kernels. The Berkeley amd is the next big NFS mount client which needs to be updated to use nmount().....but that code is messy. :) -- Craig Rodrigues rodrigc@crodrigues.org