From: David Feuer <David_Feuer@brown.edu>
To: linux-kernel@vger.kernel.org
Subject: Re: [BUG] Inconsistent behaviour of rmdir
Date: Thu, 16 Nov 2000 16:17:31 -0500 [thread overview]
Message-ID: <4.3.2.7.2.20001116161327.00b2f810@postoffice.brown.edu> (raw)
In-Reply-To: <Pine.LNX.4.21.0011161934370.30811-100000@sisley.ri.silicom p.fr>
In-Reply-To: <Pine.GSO.4.21.0011161317120.13047-100000@weyl.math.psu.edu>
At 07:51 PM 11/16/2000 +0100, you wrote:
>Now I see your point : by "." or "foo/." you mean the directory itself,
>while "foo" or "foo/" refer to the link to the directory, and they are
>obviously different objects... at least since hard links on directories
>were introduced. Fine.
. and foo/. are also links, not directories... the directories themselves
are filesystem internal objects, and not discussed by the standard. I
didn't know that linux supported hard links to directories... Isn't that
just asking for trouble?
> > Besides, we clearly violated
> > all relevant standards - rmdir() and rename() are required to fail
> > if the last component of name happens to "." or "..".
>
>By standard, do you imply 'de facto' ? Or does any source clearly state
>this ?
It rarely hurts to violate even a written standard when it says something
like this... If it says something like this (which can only happen
intentionally, afaict) should fail, but you can do something intelligent
instead, you probably should.
--
This message has been brought to you by the letter alpha and the number pi.
Open Source: Think locally, act globally.
David Feuer
David_Feuer@brown.edu
-
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:[~2000-11-16 21:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-16 13:47 Jean-Marc Saffroy
2000-11-16 15:49 ` Linus Torvalds
2000-11-16 17:49 ` Alexander Viro
2000-11-16 18:14 ` Jean-Marc Saffroy
2000-11-16 18:28 ` Alexander Viro
2000-11-16 18:51 ` Jean-Marc Saffroy
2000-11-16 18:59 ` Alexander Viro
2000-11-16 21:17 ` David Feuer [this message]
2000-11-16 22:35 ` H. Peter Anvin
2000-11-16 23:10 ` Alexander Viro
2000-11-16 23:43 ` David Feuer
2000-11-17 0:04 ` Alexander Viro
2000-11-18 1:30 ` Nix
2000-11-18 1:58 ` Alexander Viro
2000-11-17 17:56 ` Guest section DW
2000-11-17 20:27 ` Alexander Viro
2000-11-20 8:32 ` Eric Paire
2000-11-20 9:39 ` Guest section DW
2000-11-16 16:07 Jesse Pollard
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=4.3.2.7.2.20001116161327.00b2f810@postoffice.brown.edu \
--to=david_feuer@brown.edu \
--cc=linux-kernel@vger.kernel.org \
/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®