From: Peter Staubach <staubach@redhat.com>
To: "Lever, Charles" <Charles.Lever@netapp.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>, nfs@lists.sourceforge.net
Subject: Re: historical question: nfs_rename()
Date: Tue, 18 Oct 2005 14:03:01 -0400 [thread overview]
Message-ID: <435538D5.7080202@redhat.com> (raw)
In-Reply-To: <044B81DE141D7443BCE91E8F44B3C1E288E579@exsvl02.hq.netapp.com>
Lever, Charles wrote:
>>Actually, this case should fail with EISDIR, as it does. Mixing
>>directory and files in a rename(2) will fail with EISDIR or ENOTDIR.
>>
>>However, renaming one directory to another directory, when the target
>>directory is "empty", should not fail.
>>
>>
>
>the specific case i'm whining about today is renaming a directory to an
>empty directory. the desired semantic is that the empty directory will
>be replaced. the existing semantic on the Linux NFS client is that
>rename(2) returns -EBUSY.
>
>as far as we can tell, the Solaris client works as desired. the issue
>is a portability problem that arises because Linux's rename(2) doesn't
>work precisely the same way as Solaris'.
>
>
I think that this is actually a POSIX/SUS3 thing...
Thanx...
ps
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-10-18 18:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-18 17:59 historical question: nfs_rename() Lever, Charles
2005-10-18 18:03 ` Peter Staubach [this message]
2005-10-18 18:11 ` Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2005-10-18 18:15 Lever, Charles
2005-10-18 18:36 ` Trond Myklebust
2005-10-17 19:12 Lever, Charles
2005-10-17 19:18 ` Peter Staubach
2005-10-18 16:10 ` Trond Myklebust
2005-10-18 16:57 ` Peter Staubach
2005-10-18 18:06 ` 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=435538D5.7080202@redhat.com \
--to=staubach@redhat.com \
--cc=Charles.Lever@netapp.com \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.