It looks like roomkey.com doesn't seem to have any mobile apps, which makes it hard to say that it's more convenient to use when traveling than an aggregator that does have an app.
It's interesting to hear about your site though, perhaps I'll try it out next time I'm traveling.
EV_ONESHOT refers to the individual kevent registration, and is basically an automatic EV_DELETE on delivery of the event.
EPOLLEXCLUSIVE is acting at a different layer - in kevent terms it would cause only one of the registered kevents watching an object to be activated when the object is ready instead of all of the kevents watching for the same thing.
This is one reason why OS X enforces a hard page-zero on 64-bit programs - it is a hard error to map or allocate anything in the lowest 4 GB of memory, so programmers will immediately discover pointer truncation bugs when porting 32-bit code to 64-bit.
This is true - the compatibility boundary for OS X is at the link-against-libSystem layer. The actual interface between libSystem and the kernel is private to Apple and is not guaranteed to stay argument or ABI compatible. (this includes the syscall() function)
Several xnu syscalls are actually paired with a userspace wrapper function that does some extra stuff. Existing syscalls may even become wrapped in a subsequent release if needed.
And a bunch of those are using Wine, which requires mapping code at the zero page, so they're compiled with a special load command that allows them to map the zero page.
On Yosemite, 64-bit binaries aren't allowed to do this.
That's just the syscall for waiting for a semaphore to be signaled. Most likely the crash is due to the main thread waiting for too long on that semaphore - it's likely stuck waiting for a network request to complete, and the watchdog kicked in and killed it.
IIRC the Spotlight metadata is stored per-volume, so if you for example mount an encrypted DMG or external disk the metadata for files on that volume are stored on the same volume. This way you can have separate volumes for things with different classifications, and information doesn't leak from one to the other via Spotlight.
If you strongly need full privacy separation between contexts, set up a virtual machine for your confidential work, and encrypt that. Then you can monitor what crosses the security boundary yourself, and deleting the VM means the data and any possible fragments of that data generated by nosy operating system features are gone.
Side note: Check out Finder's advanced preferences for 'Empty Trash Securely'. Additionally, I believe the swap space is now encrypted by default on Lion (at least for laptops), even if you don't have full disk encryption enabled.
It's possible to get iTunes to change its idea of where the music files are. I've done a similar amount of iTunes library moving, and it's been quite amazingly reliable through all that upheaval.
A combination of consolidating and setting the default media location and re-consolidating and holding option on launch etc will eventually get it to find all its media.
This interesting article ("What Colour are your bits?") goes in depth on some of the reasons that different licenses on the same bits can happen:
http://ansuz.sooke.bc.ca/entry/23
You can redownload: music, apps, books, TV shows. Movies aren't in that list. Also, you might not be able to redownload something if it's been taken off the store.
I'm not sure I see the difference between a log-structured file system and what they have proposed for their robust disk update strategy, especially when you add integrity streams into the picture. Anyone with more filesystems knowledge than me want to clarify this?
https://developer.apple.com/library/archive/documentation/Pe...
https://developer.apple.com/library/archive/documentation/Pe...