SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm running Slackware 12.1 and I'd like to assign fixed udp and tcp port numbers to nlockmgr. I can't find any documentation on how to do this in Slackware. I have found things suggested for other distributions but none of them seem to apply (basically they specify files to edit). I'd also like to know how nlockmgr gets started. I have all the other processes that show up for rpcinfo -p using fixed ports. I want to get them all set up with fixed port numbers so that I can use those port numbers in a set of firewall rules.
I think maybe the problem is that lockd is not configured as as a loadable module. When I do a make menuconfig I can not determine what I need to change to make lockd a loadable module. Can anyone tell me where to specify this? I know how to compile the kernel and make the modules, just not what I need to change/specify.
I'm not sure where that is in the config (I'll poke around in a bit), but for the time being, you can use kernel appends to do the same thing. In lilo.conf, put this:
append = "lockd.nlm_tcpport=4045 lockd.nlm_udpport=4045"
I have no idea how to tune whether LOCKD is modular or not, unless you edit the .config file directly. Pat's .config looks like this:
# CONFIG_NFS_V3_ACL is not set
# CONFIG_NFS_V4 is not set
# CONFIG_NFSD_V3_ACL is not set
so I would expect CONFIG_LOCKD would be in the Network File Systems menu. However, it's not. A search for LOCKD in menuconfig doesn't tell where it's located either, so all I can say is "good luck" :-)
I'm upgrading to Slackware 13.1 and getting lockd built as a module now requires that NFS client support be specified as a module under File Systems -> Network File Systems when rebuilding the kernel. NFS server support is still required to be built as a module as well (but that's the default for 13.1).
I hope this helps anyone else trying to build lockd as a module.