Sponsored Content
Operating Systems Linux SuSE problem of readdir on IA64 suse Post 302348520 by Corona688 on Friday 28th of August 2009 01:23:58 PM
Old 08-28-2009
man 3 readdir gives me this:
Code:
       On Linux, the dirent structure is defined as follows:

           struct dirent {
               ino_t          d_ino;       /* inode number */
               off_t          d_off;       /* offset to the next dirent */
               unsigned short d_reclen;    /* length of this record */
               unsigned char  d_type;      /* type of file; not supported
                                              by all file system types */
               char           d_name[256]; /* filename */
           };

So it may not be the architecture per se, but the filesystem. Not something to be depended on in any case.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

SuSE 8.1 NIC problem

i have just installed suse 8.1 on a third computer which has an Asus p4s8x with onboard NIC and sound. now, on install suse detected everything automatically with no probelm, however upon reboot the sound failed to load as well as the network card. /dev/eth* doesnt exist. i looked in the bios and... (2 Replies)
Discussion started by: norsk hedensk
2 Replies

2. UNIX for Dummies Questions & Answers

suse 9.0 problem video

i got a NV11 geForce2 100/200 and suse 9.0 pro boot the kernal but then the screen goes blank and nothing else can't install suse 9.0 pro and grabs for this problem x will not come up at all just the boot screen with rez and so on but once i tell it to install thats i have a nec multisync... (6 Replies)
Discussion started by: 3bumbs plumming
6 Replies

3. SuSE

SuSE parted problem

Hello, So, I burned the 5 cds of SuSE 10.1, and would really like to begin installation. But when I get to the partitioning phase, I get an error message saying the first hard drive is unreadable by parted, and that I'll have to use Yast instead. It also tells me I wont be able to move delete... (0 Replies)
Discussion started by: Mudrack
0 Replies

4. UNIX for Dummies Questions & Answers

how to man readdir(3)

I read the description of the command readdir by using 'man readdir'. However, in the description i was suggesed to refer to readdir(3). I wonder how to see the manual of readdir(3) Thanks (1 Reply)
Discussion started by: cy163
1 Replies

5. Programming

Finding wildcards in readdir

I am having a hard time doing this and can't seem to find an example to help me. This is my code: DIR *dirp=opendir(pathname); struct stat filebuf; struct dirent entry; struct dirent *dp=&entry; RWCString pattern; for (int i = 0; i < request_->getNumStreams(); i++) { ... (2 Replies)
Discussion started by: ajgwin
2 Replies

6. SuSE

GUI problem with Suse Linux

hi Guys,, Am very new to Linux OS.. This is my first experience with Linux. I have installed linux suse 10 in my laptop.it was working fine.. suddenly after 3 days,(i was changing some options of the already installed linux) when i login, i am getting only command interface and GUI is not... (2 Replies)
Discussion started by: mac4rfree
2 Replies

7. Shell Programming and Scripting

grep readdir

Quick question. I can not get the context corrert on this code. opendir(DIR, "."); @fileldiv = grep(/l*/,readdir(DIR)); closedir(DIR); I am trying to search all html files within a dir that start with l. Thanks for your help. (1 Reply)
Discussion started by: mrlayance
1 Replies

8. Programming

Problem shmat in HP-UX Titanium ia64. EINVAL Error

I have a process that needs two active connections to the same zone of shared memory simultaneously. The firs conection works ok, but when i do the second call to shmat it give me error 22 (EINVAL). Only works ok the second call to shmat if i disconnect the first connection (shmdt) Steps:... (3 Replies)
Discussion started by: dairby
3 Replies

9. Filesystems, Disks and Memory

RAID Problem on SUSE 11.0

I setup a RAID 5 with 5 drives, one failed, hardware failure so I physically removed it from the raid after powering the machine off then powered it back on and my raid was still good but no 5th drive. I built a 5th drive from scratch and added it in the raid thinking the raid would go into... (0 Replies)
Discussion started by: lacakid
0 Replies

10. Emergency UNIX and Linux Support

Gbrowse and GD installation in ia64 linux problem facing...

Hi all, I'm trying to install of Gbrowse recently. Unfortunately, I stuck at the step to install GD which are prerequisite for Gbrowse installation. I got try to install it, but it seems like got a lot of error message occurred :( And still can't fix the problem yet. I'm using ia64 linux... (10 Replies)
Discussion started by: patrick87
10 Replies
READDIR(3)						     Linux Programmer's Manual							READDIR(3)

NAME
readdir, readdir_r - read a directory SYNOPSIS
#include <dirent.h> struct dirent *readdir(DIR *dirp); int readdir_r(DIR *dirp, struct dirent *entry, struct dirent **result); Feature Test Macro Requirements for glibc (see feature_test_macros(7)): readdir_r(): _POSIX_C_SOURCE >= 1 || _XOPEN_SOURCE || _BSD_SOURCE || _SVID_SOURCE || _POSIX_SOURCE DESCRIPTION
The readdir() function returns a pointer to a dirent structure representing the next directory entry in the directory stream pointed to by dirp. It returns NULL on reaching the end of the directory stream or if an error occurred. On Linux, the dirent structure is defined as follows: struct dirent { ino_t d_ino; /* inode number */ off_t d_off; /* offset to the next dirent */ unsigned short d_reclen; /* length of this record */ unsigned char d_type; /* type of file; not supported by all file system types */ char d_name[256]; /* filename */ }; The only fields in the dirent structure that are mandated by POSIX.1 are: d_name[], of unspecified size, with at most NAME_MAX characters preceding the terminating null byte; and (as an XSI extension) d_ino. The other fields are unstandardized, and not present on all systems; see NOTES below for some further details. The data returned by readdir() may be overwritten by subsequent calls to readdir() for the same directory stream. The readdir_r() function is a reentrant version of readdir(). It reads the next directory entry from the directory stream dirp, and returns it in the caller-allocated buffer pointed to by entry. (See NOTES for information on allocating this buffer.) A pointer to the returned item is placed in *result; if the end of the directory stream was encountered, then NULL is instead returned in *result. RETURN VALUE
On success, readdir() returns a pointer to a dirent structure. (This structure may be statically allocated; do not attempt to free(3) it.) If the end of the directory stream is reached, NULL is returned and errno is not changed. If an error occurs, NULL is returned and errno is set appropriately. The readdir_r() function returns 0 on success. On error, it returns a positive error number. If the end of the directory stream is reached, readdir_r() returns 0, and returns NULL in *result. ERRORS
EBADF Invalid directory stream descriptor dirp. CONFORMING TO
SVr4, 4.3BSD, POSIX.1-2001. NOTES
Only the fields d_name and d_ino are specified in POSIX.1-2001. The remaining fields are available on many, but not all systems. Under glibc, programs can check for the availability of the fields not defined in POSIX.1 by testing whether the macros _DIRENT_HAVE_D_NAMLEN, _DIRENT_HAVE_D_RECLEN, _DIRENT_HAVE_D_OFF, or _DIRENT_HAVE_D_TYPE are defined. Other than Linux, the d_type field is available mainly only on BSD systems. This field makes it possible to avoid the expense of calling lstat(2) if further actions depend on the type of the file. If the _BSD_SOURCE feature test macro is defined, then glibc defines the fol- lowing macro constants for the value returned in d_type: DT_BLK This is a block device. DT_CHR This is a character device. DT_DIR This is a directory. DT_FIFO This is a named pipe (FIFO). DT_LNK This is a symbolic link. DT_REG This is a regular file. DT_SOCK This is a Unix domain socket. DT_UNKNOWN The file type is unknown. If the file type could not be determined, the value DT_UNKNOWN is returned in d_type. Currently, only some file systems (among them: Btrfs, ext2, ext3, and ext4) have full support returning the file type in d_type. All applications must properly handle a return of DT_UNKNOWN. Since POSIX.1 does not specify the size of the d_name field, and other nonstandard fields may precede that field within the dirent struc- ture, portable applications that use readdir_r() should allocate the buffer whose address is passed in entry as follows: len = offsetof(struct dirent, d_name) + pathconf(dirpath, _PC_NAME_MAX) + 1 entryp = malloc(len); (POSIX.1 requires that d_name is the last field in a struct dirent.) SEE ALSO
getdents(2), read(2), closedir(3), dirfd(3), ftw(3), offsetof(3), opendir(3), rewinddir(3), scandir(3), seekdir(3), telldir(3), fea- ture_test_macros(7) COLOPHON
This page is part of release 3.25 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. 2009-07-04 READDIR(3)
All times are GMT -4. The time now is 07:04 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy