[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Gnu-arch-users] tla1.2 on cygwin

From: lode . leroy
Subject: RE: [Gnu-arch-users] tla1.2 on cygwin
Date: Wed, 3 Mar 2004 09:11:40 +0100 (CET)
User-agent: SquirrelMail/1.4.1

Path Compression is independent of cygwin, and of NTFS.

tla compiles without modification on cygwin, so no need to port it.

(Johannes Berg is porting tla/hackerlab to win32, which is a major
undertaking. I wrote a /hack/ to make tla work on a win32 system.
I worked on a similar /hack/ to use unicode pathnames with cygwin, but did
not finish it)

The only problem for using it on FAT is that tla depends on "inode"
values, and FAT does not have them, NTFS does have a similar thing.

>require an NT based system.  Given Lode's path compression, once
>completed, everything should work in Win9x/ME.  IIRC one of his
>motivations in doing the path compression was to enable it to work
>on a FAT(32) file system.

Not realy, I don't even have a FAT partition.

To clarify for all: NTFS does support path lengths to 32000 chars, but
there's a catch.

On Windows, for each function, there is an ANSI version, and a Unicode
version. For example:
CreateFileA(char* path) and CreateFileW(w_char* path)
If one uses the CreateFileW() function, and the path starts with "\\?\"
then the path can be 32000 chars. If the path starts with something else
it is limited to 250 chars.

So most programs (being unaware of this) do not support long path names,
("most programs" include cmd.exe, explorer.exe, notepad.exe, gnuemacs.exe,

>The one caveat may be that filepermission metadata might be
>fully handled.  I know Cygwin on NT/2000/XP can use extended
>attributes on FAT to support permissions, but this still does not
>address the 9x/ME systems.
>In this case my preference would be to disallow permissions
>changes based upon the apparent permissions on these platforms.

Plaats je zoekertjes GRATIS op AdValvas
Placez votre petite annonce GRATUITEMENT sur AdValvas

reply via email to

[Prev in Thread] Current Thread [Next in Thread]