On Mon, Feb 13, 2012 at 11:42:49AM +0100, Manuel Bouyer wrote: > On Mon, Feb 13, 2012 at 10:37:25AM +0000, Emmanuel Dreyfus wrote: > > On Mon, Feb 13, 2012 at 11:27:29AM +0100, Manuel Bouyer wrote: > > > But then, if you see USER "foo.bar" in the filesystem, you don't know > > > if it should be mapped to user.foo.bar or foo.bar. > > > I don't think this can work. > > > > If the disk is from FreeBSD, you mount with -o stripxattr. When > > you read it, USER "foo.bar" becomes user.foo.bar. When you write > > user.foo.bar, it is stored as USER "foo.bar". Therefore you can use > > the Linux-like API and you will not screw up what is stored on disk. > > And what happens if you write "baz.foo.bar" ? You could just error out in > this case. Note: users and applications from OS X are not going to expect to have to write "user." to get at xattrs. I am not sure what all to recommend here as it looks like FreeBSD and Linux apps are going to want to add it. I really think Linux's way of putting the name space in the name is wrong. If these spaces are really supposed to have different symantic behavior, you should have to do different actions to get at them (i.e. flag something in the open). Take care, Bill
Attachment:
pgpneZO3gFF_F.pgp
Description: PGP signature