On Tue, Aug 14, 2012 at 11:35:02PM +0200, Pawel Jasinski wrote:
>I am sorry I did not understand your comments.
>I am also not particularly familiar with your COP. I promise to adhere
>to it in the future.
>For the patches, I can only blame bad timing. I haven't done cvs up
>before posting.
>As you
On Wed, Aug 15, 2012 at 12:42:09AM +0400, Andrey Repin wrote:
>Greetings, Christopher Faylor!
Sigh.
>>But you aren't really even suggesting that. You are apparently just
>>suggesting that every windows error should be displayed by the Cygwin
>>DLL. Wow.
>
>Um. On another hand, this made me thi
Hi Christopher,
I am sorry I did not understand your comments.
I am also not particularly familiar with your COP. I promise to adhere
to it in the future.
For the patches, I can only blame bad timing. I haven't done cvs up
before posting.
As you noticed for sure, I am also not so good with rhetori
Greetings, Christopher Faylor!
> But you aren't really even suggesting that. You are apparently just
> suggesting that every windows error should be displayed by the Cygwin
> DLL. Wow.
Um. On another hand, this made me think from my deep pit: as a regular user,
not a developer, in some cases, I
On Tue, Aug 14, 2012 at 10:37:51AM +0200, Pawel Jasinski wrote:
>Thanks guys!
>That is a great news
It isn't entirely clear that you understand that what just happened is
what we always do when we find a Windows error which we haven't
translated and for which there is better translation than EACCE
Thanks guys!
That is a great news
> cygwin1.dll returns ELIBADD natively (which, as
> of today's patches, it does)
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http
On 08/13/2012 06:07 PM, Pawel Jasinski wrote:
> hi,
>
> How about this one. Bash has already some cygwin specific stuff.
>
> rejap win7dev /usr/src/bash-4.1.10-4/src/bash-4.1
> $ diff -uN execute_cmd.c.orig execute_cmd.c
> --- execute_cmd.c.orig 2012-08-14 00:36:57.092722900 +0200
> +++ execute
On Tue, Aug 14, 2012 at 02:07:32AM +0200, Pawel Jasinski wrote:
>hi,
>
>How about this one. Bash has already some cygwin specific stuff.
>
>rejap win7dev /usr/src/bash-4.1.10-4/src/bash-4.1
>$ diff -uN execute_cmd.c.orig execute_cmd.c
>--- execute_cmd.c.orig 2012-08-14 00:36:57.092722900 +0200
>+
hi,
How about this one. Bash has already some cygwin specific stuff.
rejap win7dev /usr/src/bash-4.1.10-4/src/bash-4.1
$ diff -uN execute_cmd.c.orig execute_cmd.c
--- execute_cmd.c.orig 2012-08-14 00:36:57.092722900 +0200
+++ execute_cmd.c 2012-08-14 01:50:03.248969800 +0200
@@ -4838,6 +4
On 8/13/12 11:56 AM, Christopher Faylor wrote:
> On Mon, Aug 13, 2012 at 07:56:52PM +0200, Pawel Jasinski wrote:
>> hi guys,
>>
>> is that what we talking about (see patch below)?
>
> Thanks for the patch but I wasn't looking for a simple patch to do this.
> I said I'd make the change if someone c
On Mon, Aug 13, 2012 at 07:56:52PM +0200, Pawel Jasinski wrote:
>hi guys,
>
>is that what we talking about (see patch below)?
Thanks for the patch but I wasn't looking for a simple patch to do this.
I said I'd make the change if someone could suggest a better errno.
When I suggested a patch, it w
hi guys,
is that what we talking about (see patch below)?
If anybody is concerned about performance, I would be happy to rewrite
lookup to use some sort of hashing
I also tried to use koders.com to search for exec* and EACCES.
It doesn't look like any code indexed by koders is fishing
specificall
On 8/13/2012 9:01 AM, Corinna Vinschen wrote:
You can't be bothered to leave the high horse, right?
I like horses. Neigh, neigh as they say! :-)
Did we really sound like people *not* trying to solve this problem?
I didn't say that. All that remains is to see if you actually do solve
the proble
On Aug 13 08:49, Andrew DeFaria wrote:
> On 08/13/2012 08:22 AM, Christopher Faylor wrote:
> >But you aren't really even suggesting that. You are apparently just
> >suggesting that every windows error should be displayed by the Cygwin
> >DLL. Wow.
> I never said "every" - you did.
> >>I would dra
On 08/13/2012 08:22 AM, Christopher Faylor wrote:
But you aren't really even suggesting that. You are apparently just
suggesting that every windows error should be displayed by the Cygwin
DLL. Wow.
I never said "every" - you did.
I would draw the border at "if there's an error message".
You
On 08/13/2012 08:14 AM, Corinna Vinschen wrote:
There was an error message that cmd showed that bash did not. To me
that's suppression.
This is nonsense and you know it.
It's not nonsense. It's 100% accurate. What in my statement above is not
the truth?
It's not that the OS generates an error
On Mon, Aug 13, 2012 at 07:32:11AM -0700, Andrew DeFaria wrote:
>On 08/13/2012 01:27 AM, Corinna Vinschen wrote:
>> On Aug 12 18:49, Andrew DeFaria wrote:
>>> On 08/12/2012 01:35 PM, Earnie Boyd wrote:
On Sun, Aug 12, 2012 at 1:56 PM, Pawel Jasinski wrote:
>> If you can find a nice Linux e
On Aug 13 07:59, Andrew DeFaria wrote:
> On 08/13/2012 07:42 AM, Corinna Vinschen wrote:
> >>>There's a difference between cmd and Cygwin. Cmd is a shell, Cygwin is
> >>>just the underlying shared lib providing a generic API.
> >>OK so bash...
> >Ok so bash what?
> You were saying cmd is a shell a
On Mon, Aug 13, 2012 at 10:24:53AM +0200, Herbert Stocker wrote:
>Hi,
>
>Imho, EACCESS is indeed a bit misleading because it suggests permission
>problems. Better would be to have an EFAIL as a generic error. Actually i
>was missing an EFAIL several times when my programs needed to return
>an error
On 08/13/2012 07:42 AM, Corinna Vinschen wrote:
There's a difference between cmd and Cygwin. Cmd is a shell, Cygwin is
just the underlying shared lib providing a generic API.
OK so bash...
Ok so bash what?
You were saying cmd is a shell and Cygwin is a shared lib. So then
perhaps the responsi
On Aug 13 07:32, Andrew DeFaria wrote:
> On 08/13/2012 01:27 AM, Corinna Vinschen wrote:
> >On Aug 12 18:49, Andrew DeFaria wrote:
> >>On 08/12/2012 01:35 PM, Earnie Boyd wrote:
> >>>On Sun, Aug 12, 2012 at 1:56 PM, Pawel Jasinski wrote:
> >If you can find a nice Linux errno which maps from
>
On 08/13/2012 01:27 AM, Corinna Vinschen wrote:
On Aug 12 18:49, Andrew DeFaria wrote:
On 08/12/2012 01:35 PM, Earnie Boyd wrote:
On Sun, Aug 12, 2012 at 1:56 PM, Pawel Jasinski wrote:
If you can find a nice Linux errno which maps from ERROR_SXS_CANT_GEN_ACTCTX
to something other than EACCES I
On Aug 13 09:21, Earnie Boyd wrote:
> On Mon, Aug 13, 2012 at 9:11 AM, Corinna Vinschen> wrote:
> > On Aug 13 08:51, Earnie Boyd wrote:
> >> On Mon, Aug 13, 2012 at 4:24 AM, Herbert Stocker wrote:
> >> > There is no need for the 'no', i'd suggest ELIBBAD.
> >>
> >> Again, not an error message that
On 13/08/2012 13:51, Earnie Boyd wrote:
> On Mon, Aug 13, 2012 at 4:24 AM, Herbert Stocker wrote:
>> Hi,
>>
>> Imho, EACCESS is indeed a bit misleading because it suggests permission
>> problems. Better would be to have an EFAIL as a generic error. Actually i
>> was missing an EFAIL several times w
On Mon, Aug 13, 2012 at 9:11 AM, Corinna Vinschen> wrote:
> On Aug 13 08:51, Earnie Boyd wrote:
>> On Mon, Aug 13, 2012 at 4:24 AM, Herbert Stocker wrote:
>> > There is no need for the 'no', i'd suggest ELIBBAD.
>>
>> Again, not an error message that exec() should return.
>
> Wrong. See the Linux
On Aug 13 08:51, Earnie Boyd wrote:
> On Mon, Aug 13, 2012 at 4:24 AM, Herbert Stocker wrote:
> > There is no need for the 'no', i'd suggest ELIBBAD.
>
> Again, not an error message that exec() should return.
Wrong. See the Linux man page for execve:
http://linux.die.net/man/2/execve
ELIBBAD
On Mon, Aug 13, 2012 at 4:24 AM, Herbert Stocker wrote:
> Hi,
>
> Imho, EACCESS is indeed a bit misleading because it suggests permission
> problems. Better would be to have an EFAIL as a generic error. Actually i
> was missing an EFAIL several times when my programs needed to return
> an error cod
On 13.08.2012 10:47, Corinna Vinschen wrote:
On Aug 13 10:24, Herbert Stocker wrote:
There is no need for the 'no', i'd suggest ELIBBAD.
Not bad, either. So we have ELIBACC, ELIBBADD, and ENOPKG as
suggestions.
I'd vote against ENOPKG. That means: /* Package not installed */
A side-by-side er
On Aug 13 10:24, Herbert Stocker wrote:
> There is no need for the 'no', i'd suggest ELIBBAD.
Not bad, either. So we have ELIBACC, ELIBBADD, and ENOPKG as
suggestions.
> (And to bring back to memory, i'd also suggest to add EFAIL be added)
Here's a clear "no". EFAIL is not a useful error mess
On Aug 12 18:49, Andrew DeFaria wrote:
> On 08/12/2012 01:35 PM, Earnie Boyd wrote:
> >On Sun, Aug 12, 2012 at 1:56 PM, Pawel Jasinski wrote:
> >>>If you can find a nice Linux errno which maps from
> >>>ERROR_SXS_CANT_GEN_ACTCTX
> >>>to something other than EACCES I'd be happy to change Cygwin.
>
Hi,
Imho, EACCESS is indeed a bit misleading because it suggests permission
problems. Better would be to have an EFAIL as a generic error. Actually i
was missing an EFAIL several times when my programs needed to return
an error code that did not match well with what i found in errno.h .
On Sun,
On 08/12/2012 01:35 PM, Earnie Boyd wrote:
On Sun, Aug 12, 2012 at 1:56 PM, Pawel Jasinski wrote:
If you can find a nice Linux errno which maps from ERROR_SXS_CANT_GEN_ACTCTX
to something other than EACCES I'd be happy to change Cygwin.
Sorry I was not clear. The point was not to use linux erro
hi,
Thanks Christopher and Earnie for clearing things up.
I am trying to promote cygwin as a solution to make working with
windows better than windows.
Unfortunately I was hit by permission problem (exactly as described by
Andrew) in front of other people.
Let me say this, it did not help to promo
On Sun, Aug 12, 2012 at 04:35:23PM -0400, Earnie Boyd wrote:
>On Sun, Aug 12, 2012 at 1:56 PM, Pawel Jasinski wrote:
>>>If you can find a nice Linux errno which maps from
>>>ERROR_SXS_CANT_GEN_ACTCTX to something other than EACCES I'd be happy
>>>to change Cygwin.
>>
>>Sorry I was not clear. The p
On Sun, Aug 12, 2012 at 1:56 PM, Pawel Jasinski wrote:
>>
>> If you can find a nice Linux errno which maps from ERROR_SXS_CANT_GEN_ACTCTX
>> to something other than EACCES I'd be happy to change Cygwin.
>
> Sorry I was not clear. The point was not to use linux error code. what
> I was trying to say
hi,
On Sun, Aug 12, 2012 at 7:06 PM, Christopher Faylor wrote:
> On Sun, Aug 12, 2012 at 11:07:00AM +0200, Pawel Jasinski wrote:
>>Hi,
>>
>>>
>>> Cygwin doesn't report Windows error codes. It reports POSIX ones. I
>>> have no idea why there would be a POSIX error code for side-by-side
>>> errors
On Sun, Aug 12, 2012 at 11:07:00AM +0200, Pawel Jasinski wrote:
>Hi,
>
>>
>> Cygwin doesn't report Windows error codes. It reports POSIX ones. I
>> have no idea why there would be a POSIX error code for side-by-side
>> errors but if there were, then reporting that is more appropriate.
>>
>
>out o
Hi,
>
> Cygwin doesn't report Windows error codes. It reports POSIX ones. I
> have no idea why there would be a POSIX error code for side-by-side
> errors but if there were, then reporting that is more appropriate.
>
out of curiosity I have poked into errno.h (as well as man page) on
linux and
On 08/11/2012 12:22 PM, Christopher Faylor wrote:
On Sat, Aug 11, 2012 at 10:32:13AM -0700, Andrew DeFaria wrote:
On 08/10/2012 07:32 PM, Larry Hall (Cygwin) wrote:
On 8/10/2012 7:31 PM, Andrew DeFaria wrote:
I use Cygwin a lot. And I kick off Windows processes a lot. Recently
I've
been having
On 11/08/2012 20:22, Christopher Faylor wrote:
> On Sat, Aug 11, 2012 at 10:32:13AM -0700, Andrew DeFaria wrote:
>> On 08/10/2012 07:32 PM, Larry Hall (Cygwin) wrote:
>>> On 8/10/2012 7:31 PM, Andrew DeFaria wrote:
I use Cygwin a lot. And I kick off Windows processes a lot. Recently
I've
On Sat, Aug 11, 2012 at 10:32:13AM -0700, Andrew DeFaria wrote:
>On 08/10/2012 07:32 PM, Larry Hall (Cygwin) wrote:
>> On 8/10/2012 7:31 PM, Andrew DeFaria wrote:
>>> I use Cygwin a lot. And I kick off Windows processes a lot. Recently
>>> I've
>>> been having a problem with my system but from Cyg
On 08/10/2012 07:32 PM, Larry Hall (Cygwin) wrote:
On 8/10/2012 7:31 PM, Andrew DeFaria wrote:
I use Cygwin a lot. And I kick off Windows processes a lot. Recently
I've
been having a problem with my system but from Cygwin all I see is
"permission denied":
Ltsdo-adefaria:cd /cygdrive/c/Prog
On Fri, Aug 10, 2012 at 10:32 PM, Larry Hall (Cygwin) wrote:
> On 8/10/2012 7:31 PM, Andrew DeFaria wrote:
>>
>> I use Cygwin a lot. And I kick off Windows processes a lot. Recently I've
>> been having a problem with my system but from Cygwin all I see is
>> "permission denied":
>>
>> Ltsdo-ade
On 8/10/2012 7:31 PM, Andrew DeFaria wrote:
I use Cygwin a lot. And I kick off Windows processes a lot. Recently I've
been having a problem with my system but from Cygwin all I see is
"permission denied":
Ltsdo-adefaria:cd /cygdrive/c/Program\ Files/IBM/RationalSDLC/Clearquest
Ltsdo-adef
I use Cygwin a lot. And I kick off Windows processes a lot. Recently
I've been having a problem with my system but from Cygwin all I see is
"permission denied":
Ltsdo-adefaria:cd /cygdrive/c/Program\ Files/IBM/RationalSDLC/Clearquest
Ltsdo-adefaria:ls -l clearquest.exe
-rwxr-xr-x+ 1 Ad
45 matches
Mail list logo
