Re: O_DEFEROPEN

2000-03-26 Thread Manfred Spraul
Jamie Lokier wrote: > > They're so similar -- do we really need to very similar different > thingws. If so, let's isolate the orthognal differences and make them > work in all reasonable circumstances. Hence F_REOPEN. > Can you call F_REOPEN multiple times, or only once after open(O_DEFEROPEN)

Re: O_DEFEROPEN

2000-03-26 Thread Jamie Lokier
Matthew Kirkwood wrote: > Presumably this is so that the floppy driver can check that nobody > expects to read or write the disk while a format is in progress? > If so, I accept the need for O_NONE. No, it's so fdformat can open /dev/fd0 before fd0 knows what floppy format to use, and so it doesn

Re: O_DEFEROPEN

2000-03-26 Thread Matthew Kirkwood
On Sun, 26 Mar 2000, Jamie Lokier wrote: > > That being the case, I'd rather that O_NONE just went away. I > > am unconvinced of its worth anyway. > > Apparently it's used by fdformat and a few other small utils. Presumably this is so that the floppy driver can check that nobody expects to read

Re: O_DEFEROPEN

2000-03-26 Thread Chris Evans
On Sat, 25 Mar 2000, Jamie Lokier wrote: > O_NONE already does some kind of permission check -- you can only open a > file that has read and write access. You certainly can't open an > inaccessible file. Yes thank God. I was pretty concerned when I first saw the O_NONE thread! Many Linux ioctl