Re: "/" in filename confuses handling of spec. chars on non-managed mount

On Oct 16 16:25, ?rsek L?szl? wrote: > Hi, > > I'm running "CYGWIN_NT-5.1 1.5.24(0.156/4/2) 2007-01-31 10:57". > > If I try to create a regular file with a colon (:) in its name, cygwin > refuses it with ENOENT (rightly so): > > $ echo test >"a:b" > -bash: a:b: No such file or directory a

"/" in filename confuses handling of spec. chars on non-managed mount

Hi, I'm running "CYGWIN_NT-5.1 1.5.24(0.156/4/2) 2007-01-31 10:57". If I try to create a regular file with a colon (:) in its name, cygwin refuses it with ENOENT (rightly so): $ echo test >"a:b" -bash: a:b: No such file or directory However, if I put, in addition, a slash in the name

Re: ":" in filename

Igor Peshansky wrote: On Sat, 25 Mar 2006, Larry Hall (Cygwin) wrote: Eric Blake wrote: It would be nice if cygwin could be more proactive in recognizing : as invalid in non-managed mounts, rather than passing the : on to the Windows filename functions, in order to avoid the creation

Re: ":" in filename

On Sat, 25 Mar 2006, Larry Hall (Cygwin) wrote: > Eric Blake wrote: > > > > > It would be nice if cygwin could be more proactive in recognizing : as > > invalid in non-managed mounts, rather than passing the : on to the > > Windows filename functions, in order to avoid the creation of > > undelet

Re: ":" in filename

Eric Blake wrote: It would be nice if cygwin could be more proactive in recognizing : as invalid in non-managed mounts, rather than passing the : on to the Windows filename functions, in order to avoid the creation of undeletable filenames such as ".new." via the help of a colon, but I can l

Re: ":" in filename

"Joe Smith" wrote in message news:[EMAIL PROTECTED] "Brian Dessent" wrote in message Sorry! -^ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ:

Re: ":" in filename

"Brian Dessent" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] Hiroki Sakagami wrote: What happens in the below commands? The ":" in filenames seems to be a problem. But I don't understand the rule. The colon is used by NTFS to signify alternate data streams. You can google

Re: ":" in filename

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Brian Dessent on 3/24/2006 8:51 PM: > > The colon is used by NTFS to signify alternate data streams. You can > google for more information about this, e.g. > . And that would explain how I managed

Re: ":" in filename

Hiroki Sakagami wrote: > What happens in the below commands? The ":" in filenames seems to be > a problem. But I don't understand the rule. The colon is used by NTFS to signify alternate data streams. You can google for more information about this, e.g. .

":" in filename

Hi, What happens in the below commands? The ":" in filenames seems to be a problem. But I don't understand the rule. % ls -l total 0 % touch aaa:bbb % ls -l total 0 -rw-rw-rw- 1 anonymous anonymous 0 Mar 25 12:32 aaa % ls -l aaa:bbb -rw-rw-rw- 1 anonymous anonymous 0 Mar 25 12:32 aaa:bbb % rm a

Something funky in filename handling

97 > find . -type f -print0 | xargs -0 chmod 644 chmod: changing permissions of `./Blue_\231yster_Cult/Cities On Flame With Rock \'n\' Roll.mp3': No such file or directory (more deleted) 98 > echo $CYGWIN binmode tty ntsec codepage:oem Do I need to change my codepage to be something else? Or am