Theodore Ts'o <tytso@xxxxxxx> writes: > Or we could design an entirely new ioctl that uses a completely new > bitmask allocation scheme, or even a plan9 style set of ascii messages > which are passed back and forth between userspace and the kernel --- > or even insist that btrfs was wrong, that they shouldn't have been > allocating flags out of this legacy ioctl, but should have been using > the existing xattr interface with a new namespace that was either > btrfs specific or a new vfsflag namspace. Likely not a primary concern, but keep in mind the handful of groups attempting to provide cross-platform (and cross-filesystem) save/restore tools. (At the moment bup just saves/restores the raw attr integer, which may not be the correct approach in the long run -- metadata support is still very new, and needs further work.) Thanks for the help. -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
