Hi,
On Mon, 26 Mar 2007, Johannes Kastl wrote:
> Am 26.03.2007 19:28 schrieb [EMAIL PROTECTED]:
> > no problems here - maybe you ignored "\" being an escape character on unix ?
> >
> > vmhost:/mnt/ntfs-3g # mkdir windoze\\sucks
>
> Im think you missed the point.
>
> mkdir "windoze\ sucks"
>
> or similar seems to cause problems. So he quoted the \ instead of just
> hitting it with another \.
>
> As far as I understood.
The problem submission was misleading. What's happening is that Stavros
created a file which contained a '\' character. He can rename/move/remove
this file on Linux but he can't do anything with it on Windows.
And this is exactly the expected behaviour.
NTFS has several file namespaces: DOS, WIN32, POSIX. Linux, as a POSIX OS,
always creates files in the POSIX namespace. Characters in the file name
can be anything except '/' and '\0'. These files are accessible via the WIN
API on Windows only if they don't have "forbidden" characters. To handle
these files on Windows, the same way as on Linux, one needs to install the
Windows Services for Unix (SFU) freely available Microsoft package.
In sort, everything behaves as it was designed. No problem on Linux and all
the files are accessible if SFU is installed on Windows.
If a non-posix file namespace handling is desirable on Linux then I suggest
exporting the NTFS volume via Samba which should have support for
restricting the file namespace to the WIN32 or DOS one.
Thank you for the report, the question will be added to the ntfs-3g support
page too.
Regards,
Szaka
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
ntfs-3g-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel
