can you live with iotctl() like mechanisms to do what one might call
'out of band' signalling to say the open FD in filespace has special
properties?
could you name the filespaces to determine which settings are used?
It all seems a bit artificial to me. But if the key issue is that you
want any arbitrary process to be able to do
(f)open() ... read/write .. (f)close() on a name, then you
either dick with the name, or dick with the open FD, or invoke the gods.
sockets() in some ways was about deliberately breaking the model to
make things like ioctl() more plausibly tenable. Who really cares if
you have to setsockopt() once you bought into having to do the whole
socket() thing in the first place?
-G
