[openbeos] Re: struct stat st_mode bits
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Tue, 30 Nov 2004 16:26:54 +0100 CET
"François Revol" <revol@xxxxxxx> wrote:
> I was going through stat.h earlier, and I was wondering if anyone had
> any idea on what S_ALLOW_DUPS was supposed to be ?
> doesn't seem to be used anywhere.
BFS could use this internally, and although the original one doesn't,
my implementation actually does. It's not really needed though, so we
could think about removing it.
> Maybe we could use that bit for something useful, like Hurd's
> S_INOCACHE.
> (maybe a flag for open() would be more appropriate though.
Not that it's yet supported, but let me quote from our fcntl.h:
#define O_NOCACHE 0x00100000 /* doesn't use the file system
cache if possible */
#define O_DIRECT O_NOCACHE
I don't think that a stat flag is really appropriate here, so I think
we agree here :)
> Also I'd reconsider using S_FOO_INDEX in favor of S_INDEX, since it's
> not very scalable... we have only 2 bits left in that field.
I don't understand what you're trying to say here.
Bye,
Axel.
- Follow-Ups:
- [openbeos] Re: struct stat st_mode bits
- From: François Revol
- References:
- [openbeos] struct stat st_mode bits
- From: François Revol
Other related posts:
- » [openbeos] struct stat st_mode bits
- » [openbeos] Re: struct stat st_mode bits
- » [openbeos] Re: struct stat st_mode bits
- » [openbeos] Re: struct stat st_mode bits
- » [openbeos] Re: struct stat st_mode bits
- » [openbeos] Re: struct stat st_mode bits
- » [openbeos] Re: struct stat st_mode bits
- » [openbeos] Re: struct stat st_mode bits
- [openbeos] Re: struct stat st_mode bits
- From: François Revol
- [openbeos] struct stat st_mode bits
- From: François Revol