From: "H. J. Lu" <hjl@lucon.org>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Chip Salzenberg <chip@pobox.com>, nfs@lists.sourceforge.net
Subject: Re: Must statd be running before nfs client makes mounts?
Date: Sun, 15 Sep 2002 16:49:56 -0700 [thread overview]
Message-ID: <20020915164956.A21841@lucon.org> (raw)
In-Reply-To: <15749.5917.443602.600792@notabene.cse.unsw.edu.au>; from neilb@cse.unsw.edu.au on Mon, Sep 16, 2002 at 09:26:21AM +1000
On Mon, Sep 16, 2002 at 09:26:21AM +1000, Neil Brown wrote:
>
> (start devices, raid, etc)
> 1/ mount local filesystems
> (start network, bind, portmap)
I am thinking to write a kernel patch to set nlm_udpport and
nlm_tcpport. The current scheme works only with module and /proc
won't work with module. I'd like to be able to set ports used by
lockd according to /etc/services. In my case, I have
nlockmgr 3003/tcp
nlockmgr 3003/udp
But I have to hard code them in my kernel.
> 2/ start nfsd if appropriate
> 3/ start statd
> 4/ mount nfs filesystems
>
H.J.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-09-15 23:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-15 22:52 Must statd be running before nfs client makes mounts? Chip Salzenberg
2002-09-15 23:26 ` Neil Brown
2002-09-15 23:49 ` H. J. Lu [this message]
2002-09-16 0:00 ` Neil Brown
2002-09-16 14:12 ` H. J. Lu
2002-09-16 23:26 ` Neil Brown
2002-09-17 3:08 ` H. J. Lu
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=20020915164956.A21841@lucon.org \
--to=hjl@lucon.org \
--cc=chip@pobox.com \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.