Sponsored Content
Full Discussion: SCO Unix inode structure.
Top Forums UNIX for Dummies Questions & Answers SCO Unix inode structure. Post 302118875 by porter on Thursday 24th of May 2007 10:22:01 PM
Old 05-24-2007
struct stat from Linux looks like

Code:
struct stat {
    dev_t     st_dev;     /* ID of device containing file */
    ino_t     st_ino;     /* inode number */
    mode_t    st_mode;    /* protection */
    nlink_t   st_nlink;   /* number of hard links */
    uid_t     st_uid;     /* user ID of owner */
    gid_t     st_gid;     /* group ID of owner */
    dev_t     st_rdev;    /* device ID (if special file) */
    off_t     st_size;    /* total size, in bytes */
    blksize_t st_blksize; /* blocksize for filesystem I/O */
    blkcnt_t  st_blocks;  /* number of blocks allocated */
    time_t    st_atime;   /* time of last access */
    time_t    st_mtime;   /* time of last modification */
    time_t    st_ctime;   /* time of last status change */
};

Note, no "st_crtime".
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unix/Linux Directory Structure

Does anyone know of a good Internet source that explains the directory structure of Unix/Linux?? Thanks Gregg (2 Replies)
Discussion started by: gdboling
2 Replies

2. Filesystems, Disks and Memory

SCO TCP/IP runtime System for SCO Unix

Hi everyone i have a question for all of you. It may be basic or it may be a good one. I recently aquired a copy of "SCO TCP/IP runtime System for SCO Unix" (thats what the disks say) and for the life of me i can not get it to load. i have tried opening the disk in linux and it can not determine... (0 Replies)
Discussion started by: Cerberus
0 Replies

3. Filesystems, Disks and Memory

inode data structure

the superblock has the offset for inode table. My question is 1) whether it starts relative to the start of the first cylinder group or is it relative to the start of filesystem??? 2)and also which entry corresponds to the root(/) inode?? is it second or third entry??? My questions are... (4 Replies)
Discussion started by: anwerreyaz
4 Replies

4. UNIX for Dummies Questions & Answers

What are some benefits of the UNIX hierarchical file structure?

What are some benefits of the UNIX hierarchical file structure? I am new to UNIX and researching some information about it for a class so please help if you can. Thanks. (1 Reply)
Discussion started by: 88923JJJSDK
1 Replies

5. UNIX for Dummies Questions & Answers

Not quite related to Unix but CP/M file structure...

I'm not sure where to post this but I'm having some trouble with the directories in CP/M... I'm sorry about the length but I'm totally confused... I've seen that the directory entry in CP/M contains the following: 1 byte User Code 8 bytes Filename 3 bytes File extension 1 byte Extension 2... (3 Replies)
Discussion started by: Legend986
3 Replies

6. SCO

load sco xenix and sco unix binary ?

Hi I have some sco xenix object, bin and archive files that operate in sco unix 5.0.7. I know that sco unix kernel can support sco xenix binary. I want to know how can I link xenix and unix archives together? (0 Replies)
Discussion started by: javad1_maroofi
0 Replies

7. UNIX for Dummies Questions & Answers

UNIX command to get inode's tid and pid

Hi everyone, I am new here in www.unix.com, i found this site because I am looking for an answer to this problem of mine. I need to know a UNIX command to display an inode's thread id and process id. Hope someone can help me on this. Thanks :D (8 Replies)
Discussion started by: rodkun
8 Replies

8. Programming

Parsing unix STAT structure

Hi I am creating a utility which needs to create a log file under the path represented by an environment variable. The condition is that this path must be a valid DIRECTORY PATH. So i need to determine that the path is indeed a VALID DIRECTORY PATH. I have written a function which will return... (2 Replies)
Discussion started by: skyineyes
2 Replies

9. Shell Programming and Scripting

How can I get only FileName associated with a INODE on Unix much faster?

How can I get only FileName associated with a INODE on Unix in seconds instead of minutes, as it is the case for me as shown below. # Say I have FileDescriptor: 43, INODE: 2590784, File: abc.rdb. I want to get only filename associated with inode:2590784 and FD:43. $> time find / -inum... (7 Replies)
Discussion started by: kchinnam
7 Replies

10. Shell Programming and Scripting

Getting the Folder Structure in Unix

Hi All, I have a compute box and I want to tar directory structure under a directory and then Deploy/untar it in a new compute box so that the directory structure will be exactly the same. I do not want any of the file to be extracted and deployed but instead only the directory structure. ... (2 Replies)
Discussion started by: filter
2 Replies
stat(2) 							System Calls Manual							   stat(2)

Name
       stat, lstat, fstat - get file status

Syntax
       #include <sys/types.h>
       #include <sys/stat.h>

       stat(path, buf)
       char *path;
       struct stat *buf;

       lstat(path, buf)
       char *path;
       struct stat *buf;

       fstat(fd, buf)
       int fd;
       struct stat *buf;

Description
       The  system  call  obtains  information about the file path.  Read, write, or execute permission of the named file is not required, but all
       directories specified in the path name that leads to the file must be reachable.

       The system call is like except when a named file is a symbolic link.  In this instance, returns information about the link; returns  infor-
       mation about the file that is referenced by the link.

       The system call and the system call obtain the same information about an open file referenced by the argument descriptor.

       The buf is a pointer to a structure.  Information about a file is placed in the structure.  The contents of the structure pointed to by buf
       includes the following:
       struct stat {
	 dev_t	 st_dev;    /* device inode resides on */
	 ino_t	 st_ino;    /* this inode's number */
	 u_short st_mode;   /* protection */
	 short	 st_nlink;  /* number or hard links to the file */
	 short	 st_uid;    /* user-id of owner */
	 short	 st_gid;    /* group-id of owner */
	 dev_t	 st_rdev;   /* the device type, for inode that is device */
	 off_t	 st_size;   /* total size of file */
	 time_t  st_atime;  /* file last access time */
	 int	 st_spare1;
	 time_t  st_mtime;   /* file last modify time */
	 int	 st_spare2;
	 time_t  st_ctime;   /* file last status change time */
	 int	 st_spare3;
	 long st_blksize; /* optimal blocksize for file system i/o ops */
	 long st_blocks;  /* actual number of blocks allocated */
	 long st_spare4;
	 u_long st_gennum; /* file generation number */
	   };

       st_atime    The time when file data was last accessed.  This is changed by the system calls and For efficiency, st_atime is not set when  a
		   directory is searched.

       st_mtime    The	time  when  data  was last modified.  It is not set by changes of owner, group, link count, or mode.  It is changed by the
		   system calls and

       st_ctime    The time when file status was last changed.	It is set by writing and changing the i-node. It can be changed by  the  following
		   system calls: and

       The status information word st_mode has the following bits:
       #define S_IFMT	0170000 /* type of file */
       #define S_IFDIR	0040000 /* directory */
       #define S_IFCHR	0020000 /* character special */
       #define S_IFBLK	0060000 /* block special */
       #define S_IFREG	0100000 /* regular */
       #define S_IFLNK	0120000 /* symbolic link */
       #define S_IFSOCK 0140000 /* socket */
       #define S_IFIFO	0010000 /* FIFO - named pipe */
       #define S_ISUID	0004000 /* set user id on execution */
       #define S_ISGID	0002000 /* set group id on execution */
       #define S_ISVTX	0001000 /* save swapped text even after use */
       #define S_IREAD	0000400 /* read permission, owner */
       #define S_IWRITE 0000200 /* write permission, owner */
       #define S_IEXEC	0000100 /* execute/search permission, owner */
       The mode bits 0000070 and 0000007 encode group and others permissions.  For further information, see

       When fd is associated with a pipe, returns a buffer with only st_blksize set.

Environment
       SYSTEM_FIVE

       Unlike the System V definition, ELOOP is a possible error condition.

Restrictions
       Applying to a socket returns a zeroed buffer and [EOPNOTSUPP].

       The  fields in the stat structure marked st_spare1, st_spare2, and st_spare3 are used when inode time stamps expand to 64 bits.	This, how-
       ever, can break certain programs that depend on the time stamps being contiguous in calls to

Return Values
       Upon successful completion, a value of zero (0) is returned.  Otherwise, a value of -1 is returned and errno is set to indicate the error.

Diagnostics
       The and system calls fail if any of the following is true:

       [EACCES]       Search permission is denied for a component of the path prefix.

       [EFAULT]       The buf or name points to an invalid address.

       [EIO]	      An I/O error occurred while reading from or writing to the file system.

       [ELOOP]	      Too many symbolic links were encountered in translating the pathname.

       [ENAMETOOLONG] A component of a pathname exceeds 255 characters, or an entire path name exceeds 1023 characters.

       [ENOENT]       The named file does not exist or path points to an empty string and the environment defined is POSIX or SYSTEM_FIVE.

       [ENOTDIR]      A component of the path prefix is not a directory.

       The system call fails if one or more of the following are true:

       [EBADF]	      The fildes is not a valid open file descriptor.

       [EFAULT]       The buf points to an invalid address.

       [EIO]	      An I/O error occurred while reading from or writing to the file system.

       [EOPNOTSUPP]   The file descriptor points to a socket.

       [ETIMEDOUT]    A connect request or remote file operation failed because the connected party did not respond after a period of time  deter-
		      mined by the communications protocol.

See Also
       chmod(2), chown(2), link(2), mknod(2), read(2), unlink(2), utimes(2), write(2)

																	   stat(2)
All times are GMT -4. The time now is 03:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy