From owner-freebsd-current Sun Oct 18 09:58:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13207 for freebsd-current-outgoing; Sun, 18 Oct 1998 09:58:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13197 for ; Sun, 18 Oct 1998 09:58:15 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Spinner) with ESMTP id AAA01806; Mon, 19 Oct 1998 00:57:06 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199810181657.AAA01806@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Chuck Robey cc: freebsd-current@FreeBSD.ORG Subject: Re: mount flags In-reply-to: Your message of "Sun, 18 Oct 1998 12:48:39 -0400." Date: Mon, 19 Oct 1998 00:57:06 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: [..] > I have a very recently broke thing that was happily using a call to > statfs, to tell if it was an NFS filesystem or not. Last time I had > occasion to take a look at this, there were flags of the sort MOUNT_XXX, > where the XXX could have been UFS, MFS, NFS, etc. The application is > specifically looking for MOUNT_NFS, and it's just not around anymore, > that I can find. > > I would be happy to find it, but I suspect that the method for detecting > an NFS mounted FS has changed, so that the app should no longer use > statfs. That's kind of odd, because this port works on a lot of other > systems which seem to do that fine. What's wrong with the f_fstypename[] field in struct statfs? It'll contain a string "nfs" or "ufs" etc.. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message