On Wed, Jun 07, 2006 at 04:15:04PM +0100, Alec Muffett wrote: > > >Should it retain the directory structure for each match, e.g. > >~/.zfs/view/[EMAIL PROTECTED]/Music/A/Abba.mp3, or remap everything, e.g. > >~/.zfs/view/[EMAIL PROTECTED]/Abba.mp3? > > The former; my intent was to compute the subset of filesystem objects > which match the patterns specified, and then further include any > *extra* directory structure necessary to expose those objects - even > if it does not match the rules - so that finally all necessary > directory hierarchies are included but unnecessary ones are ignored.
But how could the filesystem know which directories to present without traversing all the way down and marking directories that contain objects relevant to the filter or directories that do? If views are dynamic then this is hard; if they're allowed to take up persistent storage then you can take a hit creating them (i.e., not O(1)) and get what you want. I think you may want to be able to filter on object types and you'll want conjunction and alternator (AND, OR) boolean operators, as well as grouping. That way you can filter directories and files separately. Typically you'd want to see all directories but only certain files. Also, why shouldn't lofs grow similar support? Nico -- _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss