This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Data streams being treated as files in Cygwin


On 11 May 2006 16:11, Igor Peshansky wrote:

> On Thu, 11 May 2006, Dave Korn wrote:
> 
>> On 11 May 2006 16:00, Igor Peshansky wrote:
>> 
>>> On Thu, 11 May 2006, Dave Korn wrote:
>> 
>>>>   Cygwin's file handling relies on the underlying facilities of the
>>>> Windows O/S, for the most part.
>>> 
>>> Yes, and that leads to some funny behavior -- see below.
>> 
>>> Interestingly enough:
>>> 
>>> $ echo "BLAH" > a:b
>>> bash: a:b: No such file or directory
>> 
>>   Perhaps you forgot to put a floppy in the drive?
> 
> Gee, you think so? :-)

  Hmmm... let's try....

dk@rainbow /test/ads> echo "blah" > a:b
bash: a:b: No medium found
dk@rainbow /test/ads>

  OK, I think I get it now.  Let me re-word my observation:

>>   Perhaps you forgot to put the floppy drive in?

> The point I was making was that Windows isn't consistent about treating
> filenames as streams vs. disk references, due to the reuse of the ':'
> character.  I'm guessing it would be possible to add streams to a file
> called 'a', but not through the interfaces used by Cygwin.

  Gee, you think not?  :-)

dk@rainbow /test/ads> echo "blah" > ./a:b
dk@rainbow /test/ads> ls -la a
-rw-r--r-- 1 dk Domain Users 0 May 11 16:16 a
dk@rainbow /test/ads>


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]