> >_If_ you want to use "add magical 4 bytes to the end of component to
> >indicate a symlink" - more power to you, but that's nothing but a
> >detail of your filesystem layout. You are making a directory with
> >both 'foo' and 'foo.!nk' invalid, but that's the matter of fsck for
> >your filesystem and ability of fs driver to cope with such error
> >gracefully.
>
> Sounds great.
>
> Now add this to NTFS, iso9660, and vfat, without directly modifying any of the three filesystems (otherwise you'd need to maintain patches for different versions of these filesystem drivers).
_I_ wouldn't need that since I'm not interested in internal business of
either of these filesystems (BTW, iso9660 is perfectly capable of supporting
symlinks - google for rockridge or just take a look at any "live fs" ISO
image from damn next to any distro).
And no, this stuff will stay on fs level. There will be no magic flag
saying "this fs has funny symlinks implementation". Consider that one
vetoed - and I _really_ doubt that going directly to Linus will give
you anything but LARTing in that case. Severe LARTing, judging by
the precedents...
If modifications for vfat and ntfs will happen to have common functions -
just put them into a library and use them in both filesystems. _If_ you
manage to convince the maintainers of VFAT and NTFS resp. that it's worth
the trouble, in the first place.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/