On Tue, Mar 22, 2016 at 11:19:51PM -0500, Steve French wrote: > On Tue, Mar 22, 2016 at 11:13 PM, Steve French <smfrench@xxxxxxxxx> wrote: > > Yes, the browser still uses it (at least on the system I tried > > yesterday), and so do a few important subsystems (the file resource > > manager for example). Presumably streams are used even more on Mac. > > > > I was experimenting with some patches in the last few weeks to list > > streams (either via an xattr as ntfs-3g does, but I am leaning toward > > an ioctl for cifs.ko). They are needed for backup (at least), and not > > just for accessing Macs (which use resource forks extensively), but > > since Windows stores the zone identifier (where a file came from is > > stored when internet explorer downloads anything) in an alternate data > > stream, and also "FCI" (file classification information) is stored > > there. Sounds like there are important user, then. > I should also note that since SMB3 operations are handle based > (except open/create itself), I prefer using an ioctl rather than xattr > query to list streams. So on Linux you'd want that ioctl to return a file descriptor for a given stream? > In addition, by overlapping the alternate > data stream name space, with the EAs name space they are > harder to tell apart (xattrs are used less frequently on Windows > than in the past but they do show up from time to time, > e.g. in their Services for Unix). Seems wrong to make it easy > to confuse streams and EAs (extended attributes). Sounds like everyone's agreed that the two should be kept distinct. --b. -- 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
