Messages in this thread | | | Date | Mon, 14 Aug 2000 09:58:32 -0600 | From | "Jeff V. Merkey" <> | Subject | Re: NTFS-like streams? |
| |
Michael Rothwell wrote: > > Horst von Brand wrote: > > > Better build specialized tools, don't hope for interoperability. It is not > > just tar(1) which is affected, it is almost every single tool tha handles > > files; and then think about exporting this gunk over NFS to an uninfected > > Unix system, and trying to handle it there... or just unpacking your NTFS > > files on a Mac filesystem, or VFAT. Fun, fun, fun. > > Why would someone even attempt to restore an NTFS volume > onto an HFS one? NFS does not currently export NTFS, Vfat, > etc. Version 4 _does_ include support for EAs. >
At present, they cannot without loosing this NT specific meta data which could render some of their applications unable to run properly. (kind of like copying Ext2 files to a vfat partition -- you loose the unix permissions when MS-DOS boots the fat file system, or W98 or NT, etc.)
> Have stat() report that the file isn't simple; provide a libc call for > copyfile() or similar, and then you've defined a system-wide standard > way of dealing with them. Tar can check for ISMULTI or whatever, and > then read the streams out (the tar format actually supports EAs, > although specific actual tools may not). Cp can check ISMULTI and with > do the copy itself, or call copyfile() if it is available (latter > preferred). > > > Easiest way out: > > Simply provide a method for accessing them using the > VFS. Like Linus' "/" idea. Or a ":". Or let the FS > tell the VFs what character it prefers. Then NTFS > could really act like NTFS. > > -M > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.rutgers.edu > Please read the FAQ at http://www.tux.org/lkml/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |