From: Kevin Ryde <user42@zip.com.au>
Subject: tasks ice-9 ftw
Date: Mon, 08 Sep 2003 08:52:56 +1000 [thread overview]
Message-ID: <874qzotdmf.fsf@zip.com.au> (raw)
I added an entry to the tasks file,
- ice-9/ftw.scm problems:
- stat-dir-readable?-proc decides the readability of a directory
by looking at "stat" information, but does so imperfectly. It
doesn't take into account supplementary group memberships
(getgroups), or that "root" can read anything, or access control
lists (on systems which have those). Just attempting an opendir
would be simpler and more reliable.
- visited?-proc tests only stat:ino, but this is not unique across
filesystems, stat:dev must be used too.
- Passing "/" to start from the root directory doesn't work, it
looks like perhaps trailing slashes are stripped too agressively.
I put it under 1.8, anyone who disagrees with that severity can move
it. Clean fixes could no doubt go into the 1.6 branch for instance,
but I'm not feeling brave enough to attack it at the moment.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
reply other threads:[~2003-09-07 22:52 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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874qzotdmf.fsf@zip.com.au \
--to=user42@zip.com.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).