-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wrong list. Redirecting.
According to Vance Turner on 5/18/2005 11:06 PM:
> I usually don't write you guys, I follow the thread to see how development
> is going.
>
> Just a note. The ls command is't quite right.
>
> Ls -lRC wil not recursively li
On Sat, May 07, 2005 at 01:25:40PM -0400, Christopher Faylor wrote:
>On Sat, May 07, 2005 at 11:08:05AM -0600, Eric Blake wrote:
>>-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 importan
On Sat, May 07, 2005 at 11:08:05AM -0600, Eric Blake wrote:
>-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 chdi
-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
On Fri, May 06, 2005 at 11:34:56PM -0700, Paul Eggert wrote:
>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?
Eric Blake alluded to it here:
http://sources.redhat.com/ml/cygwin/2005-05/msg00254.html
Bas
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.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentat
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.
Exce
>> By the way, the coreutils anon CVS mirror syncronization
>> appears to be hung again,
I've just sync'd things.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:
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.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
P
-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 on
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] == '
-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.
>
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 Thu, May 05, 2005 at 06:44:05PM +0100, 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
- Original Message -
From: "Paul Eggert" <[EMAIL PROTECTED]>
To: "Eric Blake" <[EMAIL PROTECTED]>
Cc: "Pierre A. Humblet" <[EMAIL PROTECTED]>; ;
Sent: Thursday, May 05, 2005 12:35 PM
Subject: Re: mkdir -p and network drives
> Eri
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),
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 hassl
On Thu, May 05, 2005 at 09:35:53AM -0700, 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 c
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
-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
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 direct
> O(n^2)? I see only O(n), regardless where the algorithm begins the search.
> In any path of length n, you have a constant sum of n stat and mkdir calls,
> AFAICS.
I was using n to mean the number of components separated by /, not the string
length of the path (see the source code coreutils/lib
On May 3 07:05, Eric Blake wrote:
> rather than starting at the left and
> making sure each path component exists, the algorithm could start at the
> right and successively prune each rightmost component until it no longer
> gets ENOENT (or gets to the empty string), then build back up from that
-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
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
mkdir: cannot create directory `//MACHINE': No such file or directory
This is because mkdir checks for the exis
25 matches
Mail list logo
