From: "David Dabbs" <david@dabbs.net>
To: "'ReiserFS List'" <reiserfs-list@namesys.com>,
<linux-kernel@vger.kernel.org>
Cc: <viro@parcelfarce.linux.theplanet.co.uk>
Subject: RE: Re: [PATCH] use S_ISDIR() in link_path_walk() to decide whether the last path component is a directory
Date: Mon, 13 Sep 2004 17:47:50 -0500 [thread overview]
Message-ID: <20040913224757.B2EAC15C76@mail03.powweb.com> (raw)
In-Reply-To:
> viro wrote:
>> if (*name == '/') {
>> if (*(name+1)=='/' && *(name+2)==':') {
>> name+=3;
>
> Pathname resolution is a hell of a fundamental thing and kludges
>like that are too ugly to be acceptable. If you can't make that clean
>and have to resort to stuffing "special cases" (read: barfbag of ioctl
>magnitude) into the areas that might be unspecified by POSIX, don't do it
>at all.
>
Even though SuS allows for implementation-specific resolution for pathnames
starting with "//"? It's kludgy, and I suspected that might be the response,
but I thought I'd float it nonetheless.
>I don't like the amount of handwaving from Hans, but *that* is far
>worse. Vetoed.
Kludgy, yes, but far worse? At least I bothered to take the SuS into
consideration and took the time to try an approach, however kludgy, that
might work within them.
Bilious or not, thanks for the feedback.
david
reply other threads:[~2004-09-13 22:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040913224757.B2EAC15C76@mail03.powweb.com \
--to=david@dabbs.net \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.com \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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
Powered by JetHome