212
211
<p>One is when implementing a user space file system driver that reads blocks of a block device that is already represented by the native volume monitor (for example a CD Audio file system driver). Such a driver will generate its own <a class="el" href="classGio_1_1Mount.html" title="The Mount interface represents user-visible mounts.">Mount</a> object that needs to be associated with the <a class="el" href="classGio_1_1Volume.html" title="The Volume interface represents user-visible objects that can be mounted.">Volume</a> object that represents the volume.</p>
213
212
<p>The other is for implementing a <a class="el" href="classGio_1_1VolumeMonitor.html" title="Monitors a file or directory for changes.">VolumeMonitor</a> whose sole purpose is to return <a class="el" href="classGio_1_1Volume.html" title="The Volume interface represents user-visible objects that can be mounted.">Volume</a> objects representing entries in the users "favorite servers" list or similar.</p>
214
213
<p>Deprecated: 2.20: Instead of using this function, <a class="el" href="classGio_1_1VolumeMonitor.html" title="Monitors a file or directory for changes.">VolumeMonitor</a> implementations should instead create shadow mounts with the URI of the mount they intend to adopt. See the proxy volume monitor in gvfs for an example of this. Also see g_mount_is_shadowed(), g_mount_shadow() and g_mount_unshadow() functions. </p>
217
216
<tr><td class="paramname">mount</td><td>A <a class="el" href="classGio_1_1Mount.html" title="The Mount interface represents user-visible mounts.">Mount</a> object to find a parent for. </td></tr>