From owner-freebsd-questions@FreeBSD.ORG Sat Jul 5 16:07:37 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 012821065670 for ; Sat, 5 Jul 2008 16:07:37 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from snoogles.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 8FE9E8FC0A for ; Sat, 5 Jul 2008 16:07:36 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from localhost (localhost [127.0.0.1]) by snoogles.rachie.is-a-geek.net (Postfix) with ESMTP id E922A1CD18 for ; Sat, 5 Jul 2008 07:51:28 -0800 (AKDT) From: Mel To: freebsd-questions@freebsd.org Date: Sat, 5 Jul 2008 17:50:45 +0200 User-Agent: KMail/1.9.7 References: <486ed824.Qk+B4m7i0LUfOGZZ%perryh@pluto.rain.com> In-Reply-To: <486ed824.Qk+B4m7i0LUfOGZZ%perryh@pluto.rain.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807051750.45968.fbsd.questions@rachie.is-a-geek.net> Subject: Re: mount_nfs not accepting syntax specified by its usage complaint X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 16:07:37 -0000 On Saturday 05 July 2008 04:10:44 perryh@pluto.rain.com wrote: > How does this command: > > # mount_nfs -dis -g 8 -I 512 -R 3 -r 512 -w 512 solomon:/var/spool/uucp > /solomon/uucp > > not comply with the resulting usage complaint? > > usage: mount_nfs [-234bcdiLlNPsTU] [-a maxreadahead] [-D deadthresh] > [-g maxgroups] [-I readdirsize] [-o options] [-R retrycnt] > [-r readsize] [-t timeout] [-w writesize] [-x retrans] > rhost:path node See ~ line 346 in /usr/src/sbin/mount_nfs/mount_nfs.c, in short: option 'g' has been "removed temporarily", but usage() hasn't been updated accordingly. -- Mel Problem with today's modular software: they start with the modules and never get to the software part.