Re: mkdir -p and network drives

Christopher Faylor [EMAIL PROTECTED] writes: Except that it can't be made to work correctly due to a bash bug. Which Bash bug is that? Bash bugs can be fixed. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org

Re: mkdir -p and network drives

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Christopher Faylor on 5/7/2005 9:43 AM: Which Bash bug is that? Bash is the most important program for which 'that chdir(//) is currently no different from chdir(/)'. Is that a bug in bash or in cygwin, though? The comments for

RE: mkdir -p and network drives

On Thu, 5 May 2005, Dave Korn wrote: Original Message From: Igor Pechtchanski Sent: 05 May 2005 18:20 On Thu, 5 May 2005, Paul Eggert wrote: Eric Blake [EMAIL PROTECTED] writes: //MACHINE currently generates ENOENT, whether or not there is a server on the network with that

Re: mkdir -p and network drives

Igor Pechtchanski [EMAIL PROTECTED] writes: There's always Pierre's solution of doing minimal support for stat()ing '//' and '//MACHINE', though... Yes, that's the basic idea. That's the only thing that makes sense here. ___ Bug-coreutils mailing

Re: mkdir -p and network drives

By the way, the coreutils anon CVS mirror syncronization appears to be hung again, I've just sync'd things. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils

Re: mkdir -p and network drives

On Fri, May 06, 2005 at 11:13:56AM -0700, Paul Eggert wrote: Igor Pechtchanski [EMAIL PROTECTED] writes: There's always Pierre's solution of doing minimal support for stat()ing '//' and '//MACHINE', though... Yes, that's the basic idea. That's the only thing that makes sense here. Except that

Re: mkdir -p and network drives

Eric Blake [EMAIL PROTECTED] writes: The only other approach I can think of is to special case leading // (at least on cygwin, leading // should start after //MACHINE/Share/) What happens with the file names //, //MACHINE, and //MACHINE/Share in Cygwin? Don't they appear to be directories,

Re: mkdir -p and network drives

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Paul Eggert on 5/5/2005 2:09 AM: What happens with the file names //, //MACHINE, and //MACHINE/Share in Cygwin? Don't they appear to be directories, albeit directories that you can't alter? If not, that suggests a bug in Cygwin.

Re: mkdir -p and network drives

Eric Blake [EMAIL PROTECTED] writes: //MACHINE currently generates ENOENT, whether or not there is a server on the network with that name, and mkdir(2), stat(2), and chdir(2) with an argument of //MACHINE fail. That's certainly a hassle. Let's not worry about going through zillions of lines

cvs mirror stuck and lists.gnu.org offline (was: mkdir -p and network drives)

Eric Blake wrote: By the way, the coreutils anon CVS mirror syncronization appears to be hung again, I haven't seen any of your patches show up on savannah.gnu.org since April 22nd. I think the problem is the FSF office and equipment move. Or at the least it is complicated by it. I can say

Re: mkdir -p and network drives

On Thu, 5 May 2005, Paul Eggert wrote: Eric Blake [EMAIL PROTECTED] writes: //MACHINE currently generates ENOENT, whether or not there is a server on the network with that name, and mkdir(2), stat(2), and chdir(2) with an argument of //MACHINE fail. That's certainly a hassle. Let's not

RE: mkdir -p and network drives

Original Message From: Igor Pechtchanski Sent: 05 May 2005 18:20 On Thu, 5 May 2005, Paul Eggert wrote: Eric Blake [EMAIL PROTECTED] writes: //MACHINE currently generates ENOENT, whether or not there is a server on the network with that name, and mkdir(2), stat(2), and chdir(2)

Re: mkdir -p and network drives

- Original Message - From: Paul Eggert [EMAIL PROTECTED] To: Eric Blake [EMAIL PROTECTED] Cc: Pierre A. Humblet [EMAIL PROTECTED]; cygwin@cygwin.com; bug-coreutils@gnu.org Sent: Thursday, May 05, 2005 12:35 PM Subject: Re: mkdir -p and network drives Eric Blake [EMAIL PROTECTED

Re: mkdir -p and network drives

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Paul Eggert on 5/5/2005 2:09 AM: @@ -207,8 +207,14 @@ make_path (const char *argpath, /* If we've saved the cwd and DIRPATH is an absolute pathname, we must chdir to `/' in order to enable the chdir optimization.

Re: mkdir -p and network drives

Eric Blake [EMAIL PROTECTED] writes: + if (do_chdir dirpath[0] == '/') +{ + /* POSIX says // might be special, so chdir to // if the + file name starts with exactly two slashes. */ + char const *root = // + (dirpath[1] != '/' || dirpath[2] == '/'); Oops -

Re: mkdir -p and network drives

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Paul Eggert on 5/5/2005 9:47 PM: Oops - buffer overflow bug. dirpath[2] is past the end of the string on dirpath of /, If dirpath is /, then dirpath[1] != '/' is true, so dirpath[2] isn't evaluated. Oh well - chalk that one up to me

Re: mkdir -p and network drives

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Pierre A. Humblet on 5/2/2005 9:22 PM: According to the Cygwin Faq, * Why doesn't `mkdir -p' work on a network share? Unfortunately, you cannot do something like this: bash$ mkdir -p //MACHINE/Share/path/to/new/dir