From: "Damien \"Zaide\"" <list@zaide.org>
To: nfs@lists.sourceforge.net
Subject: NFS changement between 2.6.9 and 2.6.10?
Date: Wed, 26 Jan 2005 11:44:03 +0100 [thread overview]
Message-ID: <41F77473.70501@zaide.org> (raw)
hi,
I have a nfsV3 server running linux 2.6.9, all is good when I "ls -alR"
my nfs exported directory on my client after I chroot() in this
directory and ls -alR too that well.
But when i update my server to linux 2.6.10 and "ls -alR" my nfs
directory is allways good but when I chroot() inside, my chroot command
is locked and I can't ls my nfs directory.
I have launch a sniffer and the packet seams to be send.
Do you have any informations about this? a changement beetwen 2.6.9 and
2.6.10? a patch? a bug?
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2005-01-26 10:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 10:44 Damien "Zaide" [this message]
2005-01-26 19:43 ` NFS changement between 2.6.9 and 2.6.10? Trond Myklebust
2005-01-26 19:50 ` Trond Myklebust
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=41F77473.70501@zaide.org \
--to=list@zaide.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox