The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: "Menny Hamburger" <menny@exanet.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] NLM program ID for user space NLM server
Date: Thu, 10 May 2007 20:02:37 +1000	[thread overview]
Message-ID: <17986.60861.587591.548652@notabene.brown> (raw)
In-Reply-To: message from Menny Hamburger on Thursday May 10

On Thursday May 10, menny@exanet.com wrote:
> 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

  reply	other threads:[~2007-05-10 10:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10  9:56 [PATCH] NLM program ID for user space NLM server Menny Hamburger
2007-05-10 10:02 ` Neil Brown [this message]
2007-05-10 10:59   ` Menny Hamburger
2007-05-10 13:39     ` Trond Myklebust
2007-05-10 15:30       ` Menny Hamburger
2007-05-10 16:27         ` Trond Myklebust
2007-05-10 16:45           ` Menny Hamburger
2007-05-10 17:04             ` Trond Myklebust
2007-05-10 17:11               ` Menny Hamburger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=17986.60861.587591.548652@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=menny@exanet.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox