On Oct 24, 2013, at 5:01 PM, Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx> wrote: > On Thu, 2013-10-24 at 14:32 +0000, Myklebust, Trond wrote: >> Linux xattrs are a rabid mess. > Well... might be from a technical POV, but for users they're quite > useful in some scenarios. > > >> The whole "system" namespace is something that cannot and should not ever be exposed on a network. >> The "trusted" and "user" namespaces just offer specialised storage. Why are they needed? > Well what I do is attaching integrity information to files. > > You may say now that this is similar to what btrfs will provide > anyway... but the problem with that is, that checksums are always > updated when something in the system does valid changes to the file. > > What I however want is that I really manually have to set this, so that > I notice "accidental" changes, e.g. by myself or by buggy software... > > >> If the data needs to follow the file, then store it in the file. Why do you need the filesystem to manage that for you? > ... and since this applies to arbitrary files, from text-files over > pictures, videos to binaries,... it's neither possible to store this in > the file, nor can I really track this with an database,... since > literally any program that uses such files, from the picture editor to > the file-manager would need to use such DB. Those programs need to recompute the checksum data anyway in order to verify and/or update it. Checksums that are computed by some third party application have exactly zero value for integrity checking. Trond-- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
