Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-Id: <5.2.0.9.2.20030324153435.02db0e68@pop3.cris.com>
X-Sender: rrschulz AT pop3 DOT cris DOT com
Date: Mon, 24 Mar 2003 15:38:17 -0800
To: cygwin AT cygwin DOT com
From: Randall R Schulz <rrschulz AT cris DOT com>
Subject: Re: How to decide the file type in Cygwin?
In-Reply-To: <973C11FE0E3ED41183B200508BC7774C0C95EB49@csexchange.crysta
 l.cirrus.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

Yang,

Unix file systems don't store the the type of a file system entity in 
the directory entry used to access that entity, they stored in the 
so-called "inode." Once you have a name, use the stat(2) system call to 
get its inode information. From there you'll be able to determine what 
kind of an entity it is. If you have a file descriptor, then fstat(2) 
will do the same.

Randall Schulz


At 15:27 2003-03-24, Yang, Huaichen wrote:
>I need to list all files in a folder (including sub-folder,
>recursively), and I tried some sample codes in GNU C manual, as
>follows:
>
>...
>
>The sample was working. Then I added some codes to check the
>ep->d_type (the type of the file). If it was a directory, the
>program would check the sub-folder recursively. However, I
>encountered a compiler error. The property d_type was not defined
>in the Cygwin header file dirent.h. It seems that we cannot
>distinguish the files from the directories. Is that true? Doesn't
>anybody have a good idea to do this?
>
>Thank you very much in adavance!


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/