From: HAT <ha...@fa...> - 2012-11-07 11:55:31
|
Frank Lahm <fra...@gm...>, 25 Oct 2012 16:26:33 +0200 >> commit db568ec6e05d9b7a5274b7d9a2338eaa146eb867 >> Author: Frank Lahm <fra...@go...> >> Date: Wed Oct 10 15:34:34 2012 +0200 >>>Ensure the volume path is '/' terminated and allow nested volumes >>> >>>The previos change to the way checking for duplicate and nested paths only >>>works if the path is terminated with a '/'. >>>Allow nested volumes. This was working in 2.2 and can be used eg for sharing >>>a ZFS snapshot directory of a volume. Afaict it only works with sane AFP >>>semantics by adding 'cnid sheme = tdb' to the nested volume which also >>>makes it read-only and by adding the name of the nested directory to >>>the veto name list. >> >> I understood that tdb must be used. >> Is it necessary to make it read-only? > > Because the set of CNIDs from both databases will be distinct but the > set of AppleDouble files/EAs where the CNID is stored as well is > shared. I see. I'm implementing it now. If both are tdb, does one of the two need to be read-only? -- HAT |