From: Dan Kegel <dkegel@ixiacom.com>
To: Bogdan Costescu <bogdan.costescu@iwr.uni-heidelberg.de>
Cc: "'nfs@lists.sourceforge.net'" <nfs@lists.sourceforge.net>
Subject: Re: rpc.rexd source for Linux?
Date: Mon, 21 Jul 2003 10:00:34 -0700 [thread overview]
Message-ID: <3F1C1C32.7090502@ixiacom.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0307211511590.32628-100000@kenzo.iwr.uni-heidelberg.de>
Bogdan Costescu wrote:
> On Fri, 18 Jul 2003, Dan Kegel wrote:
>
>>That got me thinking -- why not add that execve wrapper to Linux's
>>native NFS package? Then I went looking, and discovered that
>>(perhaps wisely) Linux's NFS package doesn't include 'on' or 'rpc.rexd'.
>
> I don't follow your logic here. What has on/rpc.rexd to do with NFS ?
> Sure, they are both supposed to use RPC as do lots of others (look in
> /etc/rpc), but other than this ? So why bundle on with NFS ?
Two reasons:
1. they were part of Sun's original NFS
2. they are only useful if there's a distributed filesystem like NFS in use
But if y'all think those are too weak, then that's fine, it can stay
out of the NFS package.
The question remains - has anyone seen an open source implementation
of rpc.rexd?
Thanks,
Dan
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2003-07-21 17:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 15:00 rpc.rexd source for Linux? Dan Kegel
2003-07-21 13:21 ` Bogdan Costescu
2003-07-21 17:00 ` Dan Kegel [this message]
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=3F1C1C32.7090502@ixiacom.com \
--to=dkegel@ixiacom.com \
--cc=bogdan.costescu@iwr.uni-heidelberg.de \
--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.