aglew@ccvaxa.UUCP (Andy Glew) (09/16/87)
From: aglew@ccvaxa.UUCP (Andy Glew) I am wondering what aspects of the POSIX standard impose constraints upon unusual implementations of the filesystem. Eg. instead of UNIX's directories containing lists of names and inodes, what about a filesystem that was basically just a big hash table of the entire path - directories simply being entries required to be present before subsidiary files are created, not actually containing the names of subsidiary files. Is there anything in POSIX that would prevent this? Eg2. is the extra level of indirection filename->inode required, or is it possible simply to refuse links? And so on. Andy "Krazy" Glew. Gould CSD-Urbana. USEnet: ihnp4!uiucdcs!ccvaxa!aglew 1101 E. University, Urbana, IL 61801 ARPAnet: aglew@gswd-vms.arpa I always felt that disclaimers were silly and affected, but there are people who let themselves be affected by silly things, so: my opinions are my own, and not the opinions of my employer, or any other organisation with which I am affiliated. I indicate my employer only so that other people may account for any possible bias I may have towards my employer's products or systems. Volume-Number: Volume 12, Number 24
bagwill@decuac.uucp (Bob Bagwill) (09/18/87)
From: mimsy!cvl!decuac!bagwill@rutgers.edu (Bob Bagwill) Draft 11: "The internal format of directories is implementation defined...." There must be a <dirent.h>, and a typedef DIR, and the following routines: opendir(), readdir(), rewinddir(), closedir() and a directory must be a file. How it is implemented is left up to the implementor. Volume-Number: Volume 12, Number 25