From: Wendy Cheng <wcheng@redhat.com>
To: Olaf Kirch <okir@lst.de>
Cc: nfs@lists.sourceforge.net
Subject: Re: lockd and statd
Date: Wed, 04 Apr 2007 14:49:48 -0400 [thread overview]
Message-ID: <4613F34C.2040709@redhat.com> (raw)
In-Reply-To: <200704041933.27315.okir@lst.de>
Olaf Kirch wrote:
> On Wednesday 04 April 2007 18:09, Greg Bradner wrote:
>
>> That's what I thought. But it doesn't seem to be the case with SUSE 9.3:
>>
>
> Suse uses a patch that puts statd functionality into the kernel.
> So when you switch to a non-Suse kernel, you also need to compile
> and install rpc.statd manually - and frob your init scripts so that it gets
> started.
>
I'm wondering what would be the reason(s) that the community version of
Linux statd is put in user space ? Any one cares to give either a
technical or historical explanation ?
-- Wendy
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-04-04 19:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 7:11 lockd and statd Greg Bradner
2007-04-04 12:40 ` Trond Myklebust
2007-04-04 16:09 ` Greg Bradner
2007-04-04 17:33 ` Olaf Kirch
2007-04-04 18:49 ` Wendy Cheng [this message]
2007-04-04 21:34 ` Trond Myklebust
2007-04-04 22:48 ` Wendy Cheng
2007-04-04 23:00 ` Wendy Cheng
2007-04-04 23:22 ` Trond Myklebust
2007-04-10 8:47 ` Olaf Kirch
2007-04-10 19:36 ` Trond Myklebust
2007-04-10 20:16 ` Talpey, Thomas
2007-04-04 23:25 ` Neil Brown
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=4613F34C.2040709@redhat.com \
--to=wcheng@redhat.com \
--cc=nfs@lists.sourceforge.net \
--cc=okir@lst.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 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.