From owner-freebsd-stable@FreeBSD.ORG Tue May 10 05:21:09 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F356F16A4EF for ; Tue, 10 May 2005 05:21:08 +0000 (GMT) Received: from natco8.natcotech.com (natco8.natcotech.com [205.167.142.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CC9943D4C for ; Tue, 10 May 2005 05:21:08 +0000 (GMT) (envelope-from smartweb@leadhill.net) Received: from localhost (int10.natcotech.com [192.168.1.10]) by natco8.natcotech.com (Postfix) with ESMTP id 9CF64298141 for ; Tue, 10 May 2005 00:21:07 -0500 (CDT) Received: from natco8.natcotech.com ([192.168.1.8]) by localhost (natco10 [192.168.1.9]) (amavisd-new, port 10024) with LMTP id 04641-01-3 for ; Tue, 10 May 2005 00:21:07 -0500 (CDT) Received: from ibm.nlcc.us (ldhl-ras1-dial-12-28-24-127.natcotech.com [12.28.24.127]) by natco8.natcotech.com (Postfix) with ESMTP id 1892C298081 for ; Tue, 10 May 2005 00:21:07 -0500 (CDT) Received: (qmail 42526 invoked by uid 89); 10 May 2005 05:21:06 -0000 Received: from unknown (HELO ?192.168.0.2?) (billy@192.168.0.2) by ibm.nlcc.us with SMTP; 10 May 2005 05:21:06 -0000 Message-ID: <428044C2.80208@leadhill.net> Date: Tue, 10 May 2005 00:21:06 -0500 From: Billy Newsom User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4280353B.8050306@leadhill.net> <42803B66.3070200@alumni.rice.edu> In-Reply-To: <42803B66.3070200@alumni.rice.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at natco9.natcotech.com Subject: Re: nfs bug & df: Can I lock up my kernel and overflow this buffer? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 May 2005 05:21:09 -0000 Jonathan Noack wrote: > On 05/09/05 23:14, Billy Newsom wrote: > > From the fstab(5) man page: > "The fourth field, (fs_mntops), describes the mount options associated > with the file system. It is formatted as a comma separated list of > options. It contains at least the type of mount (see fs_type below) > plus any additional options appropriate to the file system type. See > the options flag (-o) in the mount(8) page and the file system specific > page, such as mount_nfs(8), for additional options that may be specified." That is how I read the man page, too, long ago. But when I tried the -o option on the commandline, I was unable to send mount all of the mount_nfs commandline switches I needed. I either misunderstand the mount -o option, or it doesn't work for all of the mount_nfs stuff I tried to send it. In other words, the -o option seems to not like any of the many switches understood by mount_nfs .... hence I seemed to be forced to use mount_nfs directly. And that precludes using it in fstab. > What trouble did you have with fstab? You can specify as many options > as you want as long as you separate them with commas (I think putting a > '=' between an option and its value is also necessary, although I don't > know for sure). For you it should look like this (assuming you want > read/write): > > dell:/nfs /dellbak nfs rw,-s,-x=2,-T 0 0 > I don't know. Since mount wasn't able to understand those switches on the commandline, I never tried anything in fstab, for the sake of not causing any problems with my boot. Anyone tried that sort of stuff in fstab? I'm a little skeptical. Thanks. BN