Mail Archives: cygwin-developers/1998/09/18/18:48:01
What's wrong with
.. -rwxrwxrwx bash.exe
.. lrwxrwxrwx bash.exe bin sh
Two spaces word separator 1 space dir separator for links or maybe # for dir seperator
.. drwxrwsrws usr/
.. cr--r--r-- tty1
files begining with a .SPACE are illegal under win32 anyway
try creating .SPACE.bashrc in explorer or a regular DOS box ;^)
Of course the .dll would have to be able to coordinate the
Permissions with the underlying FS permission bits, and update
them on a stat if they have changed, but this would work on any LFN FS
and links would be a 0 length file instead of 64k each
files NOT begining with a .SPACE would only be accessable
to root and the owner, and a few details like that,
and this does make LFNs only 241 chars long. ;^)
but I think eliminating 90% of the stats and opens
would speed things up enough to be worth while.
actually you could probably get by with 2 or 3
characters for permissions at most, if you planed
them out correctly since there are 100+ legal chars
for filenames.
Just an idea.
On Fri, 18 Sep 1998 16:24:58 -0400, you wrote:
>On Fri, Sep 18, 1998 at 03:08:33PM -0500, Parker, Ron wrote:
>>To answer your question, I will have to look at some old code I wrote at
>>home for accessing LFNs under DOS. I do not have e-mail there. So, I
>>will try to get back to you on Monday.
>>
>>I was curious. How could this be used to our advantage w/o a device
>>driver to modify VFATs behavior? And, how how would this address the
>>NT/9x network problem?
>
>I know that there is more information than just LFNs there. I was
>wondering if the layout had any possibilities for extra fields.
- Raw text -