>> >> The problem is deeper that the mere permissions. The permissions only look >> at the POSIX permissions returned by fstat/stat, but it does not respect the >> current user. > > Yes, it's something like that. > >> The problem you find is rather that all the other FS primitives do not know >> how to deal with permissions. >> The following code yields an error since the primitive signals a "Directory >> Not Found" which should not happen: >> >> (FileSystem root / 'lost+found') exists >> ifTrue: [ (FileSystem root / 'lost+found') hasChildren ]. > > No, they do work, but the base permission information (as far as I could see, > it's only retrieved with getting directory entries) is unusable. It's the > overall POSIX data, but without the ownership and anyway to correlate pharo > ownership and file ownership. > > Anybody to explain me how to write NB code to call directly stat/fstat? I > find this failure to be really embarassing for Pharo.
be lucky that there even IS support for permissions ;), but yeah for me this is also hard to understand that for years there hasn't been support for this :/
