From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: BuraphaLinux Server <buraphalinuxserver@gmail.com>
Cc: linux-kernel@vger.kernel.org, okir@monad.swb.de
Subject: Re: nlm_udpport vs. udpport vs lockd.nlm_udpport vs etc.
Date: Fri, 13 Jan 2006 22:33:09 -0800 [thread overview]
Message-ID: <20060113223309.011188f1.rdunlap@xenotime.net> (raw)
In-Reply-To: <5d75f4610601132130s4870d9eaq9261450905d6b888@mail.gmail.com>
On Sat, 14 Jan 2006 12:30:18 +0700 BuraphaLinux Server wrote:
> I am attempting to setup a firewall for an NFS v3 server. I need to know where
> the lockd ports will be. I have added an append line to my lilo.conf
> that looks like
> this, and it was working in the 2.4 kernels:
>
> append="lockd.nlm_udpport=32768 lockd.nlm_tcpport=32768"
>
> I am using kernel 2.6.15 from ftp.kernel.org and I am trying to learn
> what to do.
> But the file fs/lockd/svc.c seems to want this without the 'lock.' in front.
> But the file Documentation/kernel-parameters.txt suggests
> lockd.udpport and lockd.tcpport (no "nlm_").
OK, I'll send a patch for that this weekend. It should be:
lockd.nlm_udpport=N lockd.nlm_tcpport=M
when built into the kernel
image. If built as loadable modules, it is just
modprobe lockd nlm_udpport=N nlm_tcpport=M
> 1. Why do the files in the kernel disagree with each other?
No idea.
> 2. What do I really need on my append="" line, or is there some other
> way to set this now?
> 3. Should I hardcode the ports in the kernel source code and recompile?
If above doesn't work, it would be much better if you filed a bug on it.
---
~Randy
next prev parent reply other threads:[~2006-01-14 6:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-14 5:30 BuraphaLinux Server
2006-01-14 6:33 ` Randy.Dunlap [this message]
2006-01-14 7:02 ` [PATCH] nlm kernel-parameters update Randy.Dunlap
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=20060113223309.011188f1.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=buraphalinuxserver@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=okir@monad.swb.de \
/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
all inboxes | Powered by JetHome®