什么是文件系统的POSIX合规性? [英] what is posix compliance for filesystem?
问题描述
我在这方面没有什么问题,
1.所有的文件系统都需要符合posix吗?
2.是否还要求应用程序符合posix?
3.是否有任何非posix文件系统?
在require POSIX filesystem semantics通常意味着:
$ ul
有时它也意味着符号链接/硬链接支持以及文件名和32位文件指针(最小值)。在某些情况下,它也用于引用特定的API功能,如 fcntl()
锁定, mmap()
或 truncate()
或AIO。
Posix compliance is a standard that is been followed by many a companies. I have few question around this area, 1. does all the file systems need to be posix compliant? 2. are applications also required to be posix compliant? 3. are there any non posix filesystems?
In the area of "requires POSIX filesystem semantics" what is typically meant is:
- allows hierarchical file names and resolution (., .., ...)
- supports at least close-to-open semantics
- umask/unix permissions, 3 filetimes
- 8bit byte support
- supports atomic renames on same filesystem
- fsync()/dirfsync() durability gurantee/limitation
- supports multi-user protection (resizing file returns 0 bytes not junk)
- rename and delete open files (Windows does not do that)
- file names supporting all bytes beside '/' and \0
Sometimes it also means symlink/hardlink support as well as file names and 32bit file pointers (minimum). In some cases it is also used to refer specific API features like fcntl()
locking, mmap()
or truncate()
or AIO.
这篇关于什么是文件系统的POSIX合规性?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!