public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@ecoscentric.com
To: ecos-patches@ecos.sourceware.org
Subject: [Issue 1000538] add a d_type field to struct dirent in fileio
Date: Thu, 03 Apr 2008 13:29:00 -0000	[thread overview]
Message-ID: <20080403132901.01C92C540D1@snape.ecoscentric.com> (raw)
In-Reply-To: <bug-1000538-104@http.bugzilla.ecoscentric.com/>

http://bugzilla.ecoscentric.com/show_bug.cgi?id=1000538





--- Comment #6 from Nick Garnett <nickg@ecoscentric.com>  2008-04-03 14:29:00 ---
My only caveats about this are that this is not POSIX compliant. However,
making it a config option probably solves that.

A more important worry is that many filesystems do not have this information to
hand in directory entries. Most UNIX filesystem, for example, only have name
and inode number. This also applies to the eCos RAM and ROM filesystems. So to
gather this information they would effectively have to do an internal stat()
operation. While it may save effort for some filesystems, it will involve
others in more.

Whether a filesystem can provide the d_type field is a property of the
filesystem, and shouldn't be imposed from the outside. So I think that in
addition to S_IFDIR or S_IFREG, any filesystem should be allowed to set d_type
to zero, meaning "don't know". This needs to be made clear in the CDL option
description, in the definition of struct dirent and in the documentation. 


-- 
Configure issuemail: http://bugzilla.ecoscentric.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the issue.

  parent reply	other threads:[~2008-04-03 13:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-1000538-104@http.bugzilla.ecoscentric.com/>
2008-04-03 12:53 ` bugzilla-daemon
2008-04-03 13:29 ` bugzilla-daemon [this message]
2008-04-21 19:49 ` [Bug " bugzilla-daemon
2008-04-23  8:32 ` bugzilla-daemon
2008-05-01  9:42 ` bugzilla-daemon

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=20080403132901.01C92C540D1@snape.ecoscentric.com \
    --to=bugzilla-daemon@ecoscentric.com \
    --cc=ecos-patches@ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).