>This whole thread is making me very pleased I didn't buy a Macbook Pro. It isn't the fact that stuff goes wrong that bugs me, it is the fact that seemingly both the problems and solutions are via "magic." Even people who claim to be very UNIX knowledgable have no idea what is going wrong...
Sounds like rationalizing the non-purchase to me.
Nothing voodoo about how OS X works. Just that nobody bothered to investigate this problem further (and that OS X sandboxing a custom component, and a recent one at that, not some standard UNIX/POSIX functionality, so not everybody is familiar with it). My guess is that the safe-boot thing lets some maintenance scripts run uninhibited by restrictions set in other run levels, which fixes the md issue.
That said, md is just a normal unix process. If you cared enough to find this out, you can see what's going one with fs_usage, you have Dtrace available and other niceties etc.
In any case, nothing unlike the numerous problems people have with the intricacies of selinux.
Sounds like rationalizing the non-purchase to me.
Nothing voodoo about how OS X works. Just that nobody bothered to investigate this problem further (and that OS X sandboxing a custom component, and a recent one at that, not some standard UNIX/POSIX functionality, so not everybody is familiar with it). My guess is that the safe-boot thing lets some maintenance scripts run uninhibited by restrictions set in other run levels, which fixes the md issue.
That said, md is just a normal unix process. If you cared enough to find this out, you can see what's going one with fs_usage, you have Dtrace available and other niceties etc.
In any case, nothing unlike the numerous problems people have with the intricacies of selinux.