On Wed, May 18, 2005 at 02:42:12PM -0400, Pierre A. Humblet wrote:
- Original Message -
From: Corinna Vinschen
To: cygwin-patches@cygwin.com
Sent: Wednesday, May 18, 2005 12:48 PM
Subject: Re: [Patch]: mkdir -p and network drives
Hi Pierre,
I don't see a reason why you moved telldir
-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 list
Here is the implementation of mkdir and rmdir with fhandlers.
To prepare the day where proc_registry will allow writes,
I have removed setting PATH_RO and an error return from path.cc
(it's all handled in the fhandlers).
I have also removed obsolete code about fhandler_cygdrive.
There is another
]
[mailto:[EMAIL PROTECTED] On Behalf Of Pierre A. Humblet
Sent: Wednesday, May 18, 2005 11:42 AM
To: cygwin-patches@cygwin.com
Subject: Re: [Patch]: mkdir -p and network drives
- Original Message -
From: Corinna Vinschen
To: cygwin-patches@cygwin.com
Sent: Wednesday, May 18, 2005 12:48 PM
Additional note
ls -lRC - not working
ls -RCl - working
If you point out the source I will fix it.
On Wed, May 18, 2005 at 10:09:35PM -0700, Vance Turner wrote:
Additional note
ls -lRC - not working
ls -RCl - working
If you point out the source I will fix it.
1) This is not a bug reporting list.
2) This does not, as far as I can tell, have anything to do with the
subject of this message.
On Fri, May 13, 2005 at 02:41:03PM +, Eric Blake wrote:
I added read-only filesystem checking to path_conv::check so the latest
snapshot seems to work fine with the latest coreutils (trixie is a
system in my home network which exports shares):
Almost. With the 20050513 snapshot and
- Original Message -
From: Corinna Vinschen [EMAIL PROTECTED]
To: cygwin-patches@cygwin.com
Sent: Wednesday, May 11, 2005 4:53 AM
Subject: Re: [Patch]: mkdir -p and network drives
I don't like the idea of isrofs being an inline function in dir.cc.
Wouldn't that be better a method
On Thu, May 12, 2005 at 03:49:21PM -0400, Pierre A. Humblet wrote:
- Original Message -
From: Corinna Vinschen [EMAIL PROTECTED]
To: cygwin-patches@cygwin.com
Sent: Wednesday, May 11, 2005 4:53 AM
Subject: Re: [Patch]: mkdir -p and network drives
I don't like the idea of isrofs being
On May 10 20:53, Pierre A. Humblet wrote:
* dir.cc (isrofs): New function.
(mkdir): Check for FH_FS and use isrofs.
(rmdir): Use isrofs.
Index: dir.cc
===
RCS file: /cvs/src/src/winsup/cygwin/dir.cc,v
On Mon, May 09, 2005 at 08:16:36PM -0400, Pierre A. Humblet wrote:
At 06:19 PM 5/9/2005 +, Eric Blake wrote:
Second, the sequence chdir(//), mkdir(machine) creates machine in the
current directory.
Old bug.
chdir(/proc), mkdir(machine) produces the same result.
And mkdir(/proc),
Pierre A. Humblet pierre at phumblet.no-ip.org writes:
Here is a patch to allow mkdir -p to easily work with network
drives and to allow future enumeration of computers and of
network drives by ls -l.
It works by defining a new FH_NETDRIVE virtual handler for
names such as // and
Original Message
From: Eric Blake
Sent: 06 May 2005 23:29
Also, what should //.. resolve to, / or //? And if it resolves to /,
should // be an entry in the readdir() of /? I would argue that //..
should resolve to //, meaning we just have two distinct roots in the
directory tree.
At 06:19 PM 5/9/2005 +, Eric Blake wrote:
Second, the sequence chdir(//), mkdir(machine) creates machine in the
current directory.
Old bug.
chdir(/proc), mkdir(machine) produces the same result.
And mkdir(/proc), mkdir(/proc/machine) creates c:\proc\machine
The fix sets errno to EROFS,
cgf wrote:
On Thu, May 05, 2005 at 10:57:08PM -0400, Pierre A. Humblet wrote:
The code should handle // correctly, but path.cc still transforms it
into /, because of the bash bug.
Is that fixed in the current bash?
AFAIK Corinna fixed it once, but the patch got lost and it's currently
not
- Original Message -
From: Christopher Faylor [EMAIL PROTECTED]
To: cygwin-patches@cygwin.com
Sent: Friday, May 06, 2005 10:22 AM
Subject: Re: [Patch]: mkdir -p and network drives
Well, that was kinda my point. If we can't remove the // handling
because
it breaks bash then adding
On Fri, May 06, 2005 at 10:55:29AM -0400, Pierre A. Humblet wrote:
- Original Message -
From: Christopher Faylor [EMAIL PROTECTED]
To: cygwin-patches@cygwin.com
Sent: Friday, May 06, 2005 10:22 AM
Subject: Re: [Patch]: mkdir -p and network drives
Well, that was kinda my point. If we
- Original Message -
From: Christopher Faylor [EMAIL PROTECTED]
To: cygwin-patches@cygwin.com
Sent: Friday, May 06, 2005 10:58 AM
Subject: Re: [Patch]: mkdir -p and network drives
On Fri, May 06, 2005 at 10:55:29AM -0400, Pierre A. Humblet wrote:
- Original Message -
From
On Fri, May 06, 2005 at 11:07:13AM -0400, Pierre A. Humblet wrote:
That's not Paul Eggert's position,
http://cygwin.com/ml/cygwin/2005-05/msg00251.html I don't expect
problems with //, we had it working in cvs for a while and only bash
had issues. Program translating // to / should already have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sigh. We need a bash maintainer.
We need to have // working for mkdir -p to work, from what I
understand of the code snippet that was sent to the list.
`mkdir -p' only uses chdir(), mkdir(), and stat() calls. For
//server/share/newdir, the strace
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I thought that Eric Blake implied that // *had* to be translated to /,
as per POSIX. I wonder how many programs out there translate a
standalone '//' to '/'.
No, POSIX requires that / be untouched, // be implementation-defined (hint
- - define it
On Fri, May 06, 2005 at 04:29:38PM -0600, Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I thought that Eric Blake implied that // *had* to be translated to /,
as per POSIX. I wonder how many programs out there translate a
standalone '//' to '/'.
No, POSIX requires that / be
On Thu, May 05, 2005 at 10:57:08PM -0400, Pierre A. Humblet wrote:
Here is a patch to allow mkdir -p to easily work with network
drives and to allow future enumeration of computers and of
network drives by ls -l.
It works by defining a new FH_NETDRIVE virtual handler for
names such as // and
23 matches
Mail list logo
