Another in the "tying up loose ends" series: My application creates either filesystem image files, or in the more common case, operates directly on a block device (USB stick).
I would prefer to be able to ensure that rump_etfs opens the underlying pathname with O_SYNC, and more importantly O_EXCL. The former I can get around by syncing before I tell the user that we're done, the latter I would like to have as insurance against $RANDOM_GUI_MIDDLEWARE deciding to mount the device while my application is dealing with it. I can also forsee someone wanting O_CLOEXEC in future. There are three approaches to how this could be done in the rump_etfs API: 1) Change the ftype argument to a bitmask and include RUMP_O_XXXX as possible flags. This is the minimal API change, but not very pretty. 2) Add a oflags argument to rump_pub_etfs_register. 3) Add a new API where instead of hostpath the caller passes in an existing file descriptor. This seems like the most flexible approach. What do you think? This is something we could do on the hackathon in November, if I don't get to it before. Martin ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ rumpkernel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rumpkernel-users
