> Absolutely against. Open flags need to be defined in common code or you are in a massive world of trouble. I'm suggesting this can be done with definitions in common code via generically named open flags. Say for example if there was defined an O_FS1, O_FS2 (someone pick a better name) exposed for an application to use that has no meaning to the VFS layer, but could be interpreted by the filesystem. Could that work?