Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760442AbXEJKDV (ORCPT ); Thu, 10 May 2007 06:03:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754123AbXEJKDO (ORCPT ); Thu, 10 May 2007 06:03:14 -0400 Received: from mx1.suse.de ([195.135.220.2]:53327 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754069AbXEJKDO (ORCPT ); Thu, 10 May 2007 06:03:14 -0400 From: Neil Brown To: "Menny Hamburger" Date: Thu, 10 May 2007 20:02:37 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17986.60861.587591.548652@notabene.brown> Cc: Subject: Re: [PATCH] NLM program ID for user space NLM server In-Reply-To: message from Menny Hamburger on Thursday May 10 References: X-Mailer: VM 7.19 under Emacs 21.4.1 X-face: [Gw_3E*Gng}4rRrKRYotwlE?.2|**#s9D Hi, > > Since the current kernel cannot be compiled with NFS client and without > lockd, it is not possible to register a user space NLM server > Without colliding with the kernel service registered in > .../fs/lockd/lockd.c. This doesn't make any sense to me at all. You can certainly have the NFS client compiled and even running without lockd running (if you mount with "-o nolock") and in that case you are free you register your owner user-space NLM server (though I'm not sure what good it would do you). And if you want to mount an NFS filesystem without "-o nolock", then you really need the kernel lockd running, or locking will not work. Can you explain what you are trying to do - I'm curious. > > +#ifndef > #define NLM_PROGRAM 100021 > +#endif Uhm... Do you mean +#ifndef NLM_PROGRAM ?? Still not sure how that helps. NeilBrown - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/