As is so often the case, you are correct about extension loading. I had recalled that when they became particular about permissions in 10.2 they also began enforcing directory restrictions (incorrectly, experimentation now demonstrates.)
While combining the mount and load operations is common practice (at least in sample code), I can see your point about minimizing the scope of 'set uid root' activity where mount does not itself require that capability. Is there a reason that the kext should be separate from the file system bundle? On Apr 9, 12:02 pm, "Amit Singh" <[EMAIL PROTECTED]> wrote: > On Apr 9, 11:24 am, "John Brisbin" <[EMAIL PROTECTED]> wrote: > > > Extensions can only be loaded from a fixed set of locations, but one > > of these is /System/Library/Filesystems. The mount tool could be made > > to load the extension from there, if necessary, and the load tool > > could be dispensed with. > > The load program is extremely simple--it does exactly one thing: load > the extension. It's a separate program on purpose because it needs to > be setuid root. You don't want to merge it with the mount program. > > Whether you can load a kernel extension does not depend on the > extension's on-disk location. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "macfuse-devel" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
