From: Andi Kleen <ak@suse.de>
To: "Jorge L. deLyra" <delyra@latt.if.usp.br>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
Andrzej Krzysztofowicz <ankry@green.mif.pg.gda.pl>,
Frank.Olsen@stonesoft.com,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Bugs in knfsd -- Problem re-exporting an NFS share
Date: Wed, 3 Jan 2001 11:52:36 +0100 [thread overview]
Message-ID: <20010103115236.A29799@gruyere.muc.suse.de> (raw)
In-Reply-To: <14930.42496.545862.426153@notabene.cse.unsw.edu.au> <Pine.LNX.3.96.1010103082044.20347B-100000@latt.if.usp.br>
In-Reply-To: <Pine.LNX.3.96.1010103082044.20347B-100000@latt.if.usp.br>; from delyra@latt.if.usp.br on Wed, Jan 03, 2001 at 08:37:08AM -0200
On Wed, Jan 03, 2001 at 08:37:08AM -0200, Jorge L. deLyra wrote:
> It would be nice if a way was found to implement this feature on knfsd.
There is: just run unfsd too, bound to an own IP address to not conflict.
More efficient would probably be a proxy though that just forwards packets.
I see no reason in core NFS why multiple clients could not share a single
multiplexed mount. It could need some lockd support though.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-03 11:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 20:43 Andrzej Krzysztofowicz
2001-01-03 4:09 ` Neil Brown
2001-01-03 10:37 ` Jorge L. deLyra
2001-01-03 10:52 ` Andi Kleen [this message]
2001-01-03 11:14 ` Jorge L. deLyra
2001-01-03 12:06 ` Andi Kleen
2001-01-03 12:49 ` Jorge L. deLyra
2001-01-03 13:01 ` Andi Kleen
2001-01-03 13:56 ` Jorge L. deLyra
2001-01-06 19:22 ` Jorge L. deLyra
-- strict thread matches above, loose matches on Subject: below --
2000-12-29 17:33 Frank.Olsen
2000-12-29 21:30 ` 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=20010103115236.A29799@gruyere.muc.suse.de \
--to=ak@suse.de \
--cc=Frank.Olsen@stonesoft.com \
--cc=ankry@green.mif.pg.gda.pl \
--cc=delyra@latt.if.usp.br \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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®