I am thinking that is there was a proper API for accessing the filesystem then this problem wouldn't arise because things could be done behind the curtains inside the API, instead of having all the tools to be rewritten to know.
Think of FAT32, for example, the new filenames will be retained even if you use old tools on them. It is only if you mount it as a FAT16 volume they will be lost. Even if this is fixed for Reiser4 now. Next time someone wants to make changes like this we have the exact same problem yet again. > Just have a special name instead of a special boundary, or, better, have > a filename/pseudos/backup method that outputs everything needed to > backup the object "filename". > Hans > Linus Torvalds wrote: >>On Fri, 27 Aug 2004, Rik van Riel wrote: >> >> >>>Thing is, there is no way to distinguish between what are >>>virtual files and what are actual streams hidden inside a >>>file. You don't know what should and shouldn't be backed >>>up... >>> >>> >> >>I think that lack of distinguishing poiwer is more serious for >>directories. The more I think I think about it, the more I wonder whether >>Solaris did things right - having a special operation to "cross the >>boundary". >> >>I suspect Solaris did it that way because it's a hell of a lot easier to >>do it like that, but regardless, it would solve the issue of real >>directories having both real children _and_ the "extra streams". >> >> Linus >> >> >> >>
