From owner-svn-src-head@FreeBSD.ORG Thu May 5 23:20:17 2011 Return-Path: Delivered-To: svn-src-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 633C9106564A; Thu, 5 May 2011 23:20:17 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 81C7D8FC08; Thu, 5 May 2011 23:20:16 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEAJYvw02DaFvO/2dsb2JhbACEUKJltE6RJYEqhF0Ej0qHGodR X-IronPort-AV: E=Sophos;i="4.64,323,1301889600"; d="scan'208";a="121653977" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 05 May 2011 19:06:46 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id B9E26793A8; Thu, 5 May 2011 19:06:46 -0400 (EDT) Date: Thu, 5 May 2011 19:06:46 -0400 (EDT) From: Rick Macklem To: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= Message-ID: <1076836182.1082988.1304636806753.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <86r58dqett.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.202] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - IE7 (Win)/6.0.10_GA_2692) Cc: svn-src-head@freebsd.org, Rick Macklem , svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r221124 - in head: . sbin/mount sbin/mount_nfs sys/amd64/conf sys/fs/nfsclient sys/i386/conf sys/ia64/conf sys/nfsclient sys/pc98/conf sys/powerpc/conf sys/sparc64/conf sys/sun4v/conf X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2011 23:20:17 -0000 > Rick Macklem writes: > > Well, another way it could be handled would be to put the sysctls > > and > > the global variables they manipulate in a module shared by both > > clients, > > like sys/nfs/nfs_lock.c (module "nfslock"). Then the same sysctl > > would > > affect both clients. (I hesitate to create "yet another" module just > > to share the sysctls, but since "nfslock" is used by both clients, > > it > > should work ok, I think.) > > I don't understand why you would want to do that. Can't you just > change > "oldnfs" back to "nfs" in the old stack? > > Hmm, it occurred to me that there is currently no way to tell the > kernel > that two drivers conflict with eachother. Perhaps I should take a shot > at implementing a DRIVER_CONFLICT macro to mirror DRIVER_DEPEND. > Also, except for the SYSCTL() naming issue they don't comflict. At the moment it is perfectly ok to use both for mounts concurrently. For example, you could have the following 2 lines in your /etc/fstab: nfs-server:/sub1 /mnt nfs rw 0 0 nfs-server:/sub2 /mnt2 oldnfs rw 0 0 I don't know why you would actually choose to do this, unless you found that the old NFS client did something that worked better for "/sub2" for your purposes, but it will work fine. rick ps: The issue you pointed out in the first post is just a line in /etc/rc.d/mountcritremote that needs to be fixed. It uses a module name of "nfs" and "nfsclient" when the new NFS is "nfs" and "nfscl" (the old one is "oldnfs" and "nfsclient"). That's easy to fix. I'm just waiting for a review.