Upon closer examination, I [belatedly] find that load_fuse already produces this behavior and pops a version mismatch message if you install overtop a running version and then attempt a new mount.
I'll recenter my question and ask if there is any drawback to doing this "by hand"? Our effort is to make the process somewhat more invisible, in the case of an easy upgrade, and a little more instructive and less alarming, otherwise. -Jeff On Jun 14, 5:41 pm, Jeff Mancuso <[EMAIL PROTECTED]> wrote: > We're closely examining our MacFUSE upgrade path in preparation of > distributing MacFUSE 1.6 out to existing customers and I wanted to see > what everyone's thoughts were on upgrading. > > Tenatively, we're planning to notify the user of a need to upgrade > [after using a combination of reading the CFBundleVersion from the > kext and using sysctl to see what is actually running] - and with > approval run installer on the appropriate package [which we'll keep > inside our bundle]. However, if fuse is already loaded we'd call > kextunload on the loaded bundle. If it fails we'd notify the user > something [that isn't expandrive] is using MacFUSE and perhaps parse a > 'mount' call. If it succeeds the next mount attempt would correctly > load the updated kext. > > Are there any potential side effects to calling kextunload -b > com.google.filesystems.fuse and dealing with the success or failure of > its return value? > > -Jeff --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "macfuse-devel" group. To post to this group, send email to macfuse-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/macfuse-devel?hl=en -~----------~----~----~----~------~----~------~--~---
