>> If you need a file type, I've been collecting a list:
>
> You don't have S_IFNWK.
> GNU findutils lists this as "HP/UX" with no description.
OK, I have it now.
> Also findutils lists S_IFMPB and S_IFMPC as "V7" but you say "Coherent".
> I'm also collecting a list -- could you tell me which is appropriate,
> or is it both: "Coherent & V7".
The Linux source code mentions them for the SysV filesystem driver.
Coherent is like V7, so it makes sense that both would have these.
I've added S_IFNWK, the /bin/ls type code for BSD whiteout,
and another table for non-type bits.
You can get HP-UX information at http://docs.hp.com if you have a
modern web browser. Right now I'm on a dumb connection with NO flow
control, and I'd love to know what that says about chmod(2), chmod(1),
ls(1), and stat(2).
BTW, I believe many of these can't actually exist on disk.
Some of these (like S_IFSHAD AFAIK) are not seen by userspace.
hex name ls octal description
0000 000000 SCO out-of-service inode, BSD unknown type
1000 S_IFIFO p| 010000 fifo (named pipe)
2000 S_IFCHR c 020000 character special
3000 S_IFMPC 030000 multiplexed character device (Coherent)
4000 S_IFDIR d/ 040000 directory
5000 S_IFNAM 050000 XENIX special named file
6000 S_IFBLK b 060000 block special
7000 S_IFMPB 070000 multiplexed block device (Coherent)
8000 S_IFREG - 100000 regular
9000 S_IFCMP 110000 VxFS compressed (file?)
9000 S_IFNWK 110000 HP-UX network special
a000 S_IFLNK l@ 120000 symbolic link
b000 S_IFSHAD 130000 Solaris shadow inode for ACL
c000 S_IFSOCK s= 140000 socket (also "S_IFSOC" on VxFS)
d000 S_IFDOOR D 150000 Solaris door
e000 S_IFWHT w% 160000 BSD whiteout (not used for inode)
f000 S_IFMT 170000 mask (not used for inode)
hex name ls octal description
0200 S_ISVTX 001000 save swapped text even after use
0400 S_ISGID 002000 set group ID on execution
0400 S_ENFMT 002000 SysV forced file locking (shared w/ S_ISGID)
0800 S_CDF 004000 HP-UX hidden directory
0800 S_ISUID 004000 set user ID on execution
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/